- The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.
The result was delete. Sandstein 11:19, 26 September 2015 (UTC)
List of libvirt feature policies
- List of libvirt feature policies ( | talk | history | protect | delete | links | watch | logs | views) – ( View log · Stats)
- (Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)
This article appears to cover Linux CPU flags and has very little to do with libvirt (I am a libvirt developer). There are plenty of good resources on the internet already about Linux CPU flags (eg [1]). Richard W.M. Jones ( talk) 13:51, 11 September 2015 (UTC)
- Note: This debate has been included in the list of Computing-related deletion discussions. Toffanin ( talk) 19:48, 11 September 2015 (UTC)
- Note: This debate has been included in the list of Software-related deletion discussions. Toffanin ( talk) 19:48, 11 September 2015 (UTC)
- comment — The nominator says that the article covers Linux CPU flags, but those flags are well known hardware instruction sets for x86 microprocessors, and aren't related to GNU/Linux, or any particular operating systems. Thus that part of the nomination could be misleading. As a side note, I was expecting a former Red Hat's employee like Richard W.M. Jones to be better educated on basic concepts of computer science — or GNU/Linux and procfs. Toffanin ( talk) 20:10, 11 September 2015 (UTC)
- What a strange and unnecessary ad hominem attack. Some of these -- like 3dnow -- indicate groups of instructions, others -- like nx -- indicate other features of the hardware like fields in the page tables.
Richard W.M. Jones (
talk) 20:36, 11 September 2015 (UTC)
- Please assume good faith, it wasn't an ad hominem attack. Those flags are all standard ISA nomenclatures; they have nothing to do with GNU/Linux per se, since they are the same even on other operating systems like Windows, MacOS X, and pretty much all the BSD flavours. What I'm criticizing is not your person, but your lack of
WP:BEFORE which is misleading since libvirt explicitly supports those cpu hardware features according to the source code of the project itself:
https://github.com/libvirt/libvirt/blob/87205512565529b8baeb108e3d0fe376fc20c967/src/cpu/cpu_map.xml. Therefore the content of the page is correct, that is why I'm sceptic about your claims: you are suggesting that the page content is unrelated to its title, and even more to libvirt (but that page is not about libvirt itself) which is not true. One could argue that having such list of hardware flags supported by libvirt is non encyclopaedic enough to warrant an entry in WP — and I agree —, but that has nothing to do with cpu flags or GNU/Linux. Per
WP:DEL and
WP:AfD you should provide a better (and valid) reason for considering a list of libvirt feature policies as not notable for WP. And since a page about
Libvirt exists, you should have proposed a merge / redirect instead.
Toffanin (
talk) 21:35, 11 September 2015 (UTC)
- I don't like to throw oil an unnecessary fire, but Richard is right: these are specifically Linux's names for the CPUID feature flags (as reported in
/proc/cpuinfo). Intel and AMD use slightly different names for some of these flags. — Ruud 09:27, 12 September 2015 (UTC)
- I don't like to throw oil an unnecessary fire, but Richard is right: these are specifically Linux's names for the CPUID feature flags (as reported in
- Please assume good faith, it wasn't an ad hominem attack. Those flags are all standard ISA nomenclatures; they have nothing to do with GNU/Linux per se, since they are the same even on other operating systems like Windows, MacOS X, and pretty much all the BSD flavours. What I'm criticizing is not your person, but your lack of
WP:BEFORE which is misleading since libvirt explicitly supports those cpu hardware features according to the source code of the project itself:
https://github.com/libvirt/libvirt/blob/87205512565529b8baeb108e3d0fe376fc20c967/src/cpu/cpu_map.xml. Therefore the content of the page is correct, that is why I'm sceptic about your claims: you are suggesting that the page content is unrelated to its title, and even more to libvirt (but that page is not about libvirt itself) which is not true. One could argue that having such list of hardware flags supported by libvirt is non encyclopaedic enough to warrant an entry in WP — and I agree —, but that has nothing to do with cpu flags or GNU/Linux. Per
WP:DEL and
WP:AfD you should provide a better (and valid) reason for considering a list of libvirt feature policies as not notable for WP. And since a page about
Libvirt exists, you should have proposed a merge / redirect instead.
Toffanin (
talk) 21:35, 11 September 2015 (UTC)
- What a strange and unnecessary ad hominem attack. Some of these -- like 3dnow -- indicate groups of instructions, others -- like nx -- indicate other features of the hardware like fields in the page tables.
Richard W.M. Jones (
talk) 20:36, 11 September 2015 (UTC)
- Delete Not encyclopedic on its own, and not really worth merging to libvirt (I assume libvirt can mask some of these to help VM migration, but WP:NOTMANUAL) or CPUID (has a better table already). — Ruud 09:13, 12 September 2015 (UTC)
Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, — ☮ JAaron95 Talk 14:59, 18 September 2015 (UTC)
Please add new comments below this notice. Thanks, — ☮ JAaron95 Talk 14:59, 18 September 2015 (UTC)
- Delete Even setting aside all of the other argument's above this article does not have sufficient citations to be considered WP:VER. Even more troubling is that there was some WP:NOR done to gather this information the statement that these processor specific CPU features are called this where ever libvirt is deployed is incorrect and only applies to linux and in many cases only x86 . Andrdema ( talk) 08:26, 22 September 2015 (UTC)
- The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.
- The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.
The result was delete. Sandstein 11:19, 26 September 2015 (UTC)
List of libvirt feature policies
- List of libvirt feature policies ( | talk | history | protect | delete | links | watch | logs | views) – ( View log · Stats)
- (Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)
This article appears to cover Linux CPU flags and has very little to do with libvirt (I am a libvirt developer). There are plenty of good resources on the internet already about Linux CPU flags (eg [1]). Richard W.M. Jones ( talk) 13:51, 11 September 2015 (UTC)
- Note: This debate has been included in the list of Computing-related deletion discussions. Toffanin ( talk) 19:48, 11 September 2015 (UTC)
- Note: This debate has been included in the list of Software-related deletion discussions. Toffanin ( talk) 19:48, 11 September 2015 (UTC)
- comment — The nominator says that the article covers Linux CPU flags, but those flags are well known hardware instruction sets for x86 microprocessors, and aren't related to GNU/Linux, or any particular operating systems. Thus that part of the nomination could be misleading. As a side note, I was expecting a former Red Hat's employee like Richard W.M. Jones to be better educated on basic concepts of computer science — or GNU/Linux and procfs. Toffanin ( talk) 20:10, 11 September 2015 (UTC)
- What a strange and unnecessary ad hominem attack. Some of these -- like 3dnow -- indicate groups of instructions, others -- like nx -- indicate other features of the hardware like fields in the page tables.
Richard W.M. Jones (
talk) 20:36, 11 September 2015 (UTC)
- Please assume good faith, it wasn't an ad hominem attack. Those flags are all standard ISA nomenclatures; they have nothing to do with GNU/Linux per se, since they are the same even on other operating systems like Windows, MacOS X, and pretty much all the BSD flavours. What I'm criticizing is not your person, but your lack of
WP:BEFORE which is misleading since libvirt explicitly supports those cpu hardware features according to the source code of the project itself:
https://github.com/libvirt/libvirt/blob/87205512565529b8baeb108e3d0fe376fc20c967/src/cpu/cpu_map.xml. Therefore the content of the page is correct, that is why I'm sceptic about your claims: you are suggesting that the page content is unrelated to its title, and even more to libvirt (but that page is not about libvirt itself) which is not true. One could argue that having such list of hardware flags supported by libvirt is non encyclopaedic enough to warrant an entry in WP — and I agree —, but that has nothing to do with cpu flags or GNU/Linux. Per
WP:DEL and
WP:AfD you should provide a better (and valid) reason for considering a list of libvirt feature policies as not notable for WP. And since a page about
Libvirt exists, you should have proposed a merge / redirect instead.
Toffanin (
talk) 21:35, 11 September 2015 (UTC)
- I don't like to throw oil an unnecessary fire, but Richard is right: these are specifically Linux's names for the CPUID feature flags (as reported in
/proc/cpuinfo). Intel and AMD use slightly different names for some of these flags. — Ruud 09:27, 12 September 2015 (UTC)
- I don't like to throw oil an unnecessary fire, but Richard is right: these are specifically Linux's names for the CPUID feature flags (as reported in
- Please assume good faith, it wasn't an ad hominem attack. Those flags are all standard ISA nomenclatures; they have nothing to do with GNU/Linux per se, since they are the same even on other operating systems like Windows, MacOS X, and pretty much all the BSD flavours. What I'm criticizing is not your person, but your lack of
WP:BEFORE which is misleading since libvirt explicitly supports those cpu hardware features according to the source code of the project itself:
https://github.com/libvirt/libvirt/blob/87205512565529b8baeb108e3d0fe376fc20c967/src/cpu/cpu_map.xml. Therefore the content of the page is correct, that is why I'm sceptic about your claims: you are suggesting that the page content is unrelated to its title, and even more to libvirt (but that page is not about libvirt itself) which is not true. One could argue that having such list of hardware flags supported by libvirt is non encyclopaedic enough to warrant an entry in WP — and I agree —, but that has nothing to do with cpu flags or GNU/Linux. Per
WP:DEL and
WP:AfD you should provide a better (and valid) reason for considering a list of libvirt feature policies as not notable for WP. And since a page about
Libvirt exists, you should have proposed a merge / redirect instead.
Toffanin (
talk) 21:35, 11 September 2015 (UTC)
- What a strange and unnecessary ad hominem attack. Some of these -- like 3dnow -- indicate groups of instructions, others -- like nx -- indicate other features of the hardware like fields in the page tables.
Richard W.M. Jones (
talk) 20:36, 11 September 2015 (UTC)
- Delete Not encyclopedic on its own, and not really worth merging to libvirt (I assume libvirt can mask some of these to help VM migration, but WP:NOTMANUAL) or CPUID (has a better table already). — Ruud 09:13, 12 September 2015 (UTC)
Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, — ☮ JAaron95 Talk 14:59, 18 September 2015 (UTC)
Please add new comments below this notice. Thanks, — ☮ JAaron95 Talk 14:59, 18 September 2015 (UTC)
- Delete Even setting aside all of the other argument's above this article does not have sufficient citations to be considered WP:VER. Even more troubling is that there was some WP:NOR done to gather this information the statement that these processor specific CPU features are called this where ever libvirt is deployed is incorrect and only applies to linux and in many cases only x86 . Andrdema ( talk) 08:26, 22 September 2015 (UTC)
- The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.