[PATCH v2] winsup/doc/faq-what.xml: FAQ 1.2 Windows versions supported
enumerate Vista, 7, 8, 10 progression to be clear, and earliest server 2008; add 8.1, exclude S mode, add Cygwin32 on ARM, specify 64 bit only AMD/Intel --- winsup/doc/faq-what.xml | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml index ea8496ccbc65..77ba1c5fdd9c 100644 --- a/winsup/doc/faq-what.xml +++ b/winsup/doc/faq-what.xml @@ -30,12 +30,12 @@ They can be used from one of the provided Unix shells like bash, tcsh or zsh. What versions of Windows are supported? -Cygwin can be expected to run on all modern, released versions of Windows. -State January 2016 this includes Windows Vista, Windows Server 2008 and all -later versions of Windows up to Windows 10 and Windows Server 2016. +Cygwin can be expected to run on all modern, released versions of Windows, +from Windows Vista, 7, 8, 8.1, 10, Windows Server 2008 and all +later versions of Windows, except Windows S mode due to its limitations. The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on -released 64 bit versions of Windows, the 64 bit version of course only on -64 bit Windows. +released 64 bit versions of Windows including ARM PCs, +the 64 bit version of course only on 64 bit AMD/Intel compatible PCs. Keep in mind that Cygwin can only do as much as the underlying OS supports. Because of this, Cygwin will behave differently, and -- 2.28.0
Re: [PATCH] winsup/doc/faq-what.xml: FAQ 1.2 Windows versions supported
On 2020-09-17 16:22, Ken Brown via Cygwin-patches wrote: > On 9/17/2020 2:29 PM, Brian Inglis wrote: >> Based on thread >> https://cygwin.com/pipermail/cygwin/2020-September/246318.html >> enumerate Vista, 7, 8, 10 progression to be clear, and earliest server 2008 >> --- >> winsup/doc/faq-what.xml | 6 +++--- >> 1 file changed, 3 insertions(+), 3 deletions(-) >> >> diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml >> index ea8496ccbc65..09747532c2e8 100644 >> --- a/winsup/doc/faq-what.xml >> +++ b/winsup/doc/faq-what.xml >> @@ -30,9 +30,9 @@ They can be used from one of the provided Unix shells like >> bash, tcsh or zsh. >> What versions of Windows are supported? >> >> -Cygwin can be expected to run on all modern, released versions of >> Windows. >> -State January 2016 this includes Windows Vista, Windows Server 2008 and all >> -later versions of Windows up to Windows 10 and Windows Server 2016. >> +Cygwin can be expected to run on all modern, released versions of >> Windows, >> +from Windows Vista, 7, 8, 10, Windows Server 2008, and all >> +later versions of Windows. >> The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on >> released 64 bit versions of Windows, the 64 bit version of course only on >> 64 bit Windows. > > Since this is something that changes over time, I don't think you should drop > the date completely, though I see no reason to retain "January 2016". What > would you think of revising your patch so that the text says something like > this: > > "Cygwin can be expected to run on all modern, released versions of Windows. > As > of September 2020 this includes Windows Vista, 7, 8, 8.1, and 10, Windows > Server > 2008, and all later versions of Windows Server." No problem with adding 8.1 explicitly if deemed desirable. See suggested wording - keeping similar wording the same problem recurs each month - wanna change it monthly? ;^> Would not want to limit later versions to just Server, and omitted versions because now Server versions are like W10 updates e.g. WS version 2004, which is stupid and confusing, as it looks 16 years old! Damn you for making me think about this! ;^> We now probably have to add exclusions for Windows S and also mention ARM under Cygwin32. Anyone out there interested in starting a Cygwin Windows ARM64 port (and toolchain fixes for PE/COFF ARM64/AAarch64 machine type 0xAA64 if needed)? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in IEC units and prefixes, physical quantities in SI.]
Re: [PATCH] fhandler_proc.cc(format_proc_cpuinfo): add tsxldtrk, sev_es flags
On 9/17/2020 2:51 PM, Brian Inglis wrote: Add linux-next cpuinfo flags for Intel TSX suspend load address tracking instructions and AMD Secure Encrypted Virtualization with Encrypted State --- winsup/cygwin/fhandler_proc.cc | 8 1 file changed, 8 insertions(+) diff --git a/winsup/cygwin/fhandler_proc.cc b/winsup/cygwin/fhandler_proc.cc index 196bafd18993..6f6e8291a0ca 100644 --- a/winsup/cygwin/fhandler_proc.cc +++ b/winsup/cygwin/fhandler_proc.cc @@ -1376,6 +1376,7 @@ format_proc_cpuinfo (void *, char *) cpuid (, , , , 0x801f); ftcprint (features2, 1, "sev"); /* secure encrypted virt */ + /*ftcprint (features2, 3, "sev_es"); - print below */ } /* cpuid 0x8008 ebx */ if (maxe >= 0x8008) @@ -1400,6 +1401,12 @@ format_proc_cpuinfo (void *, char *) /* ftcprint (features1, 26, "ssb_no"); *//* ssb fixed in hardware */ } + /* cpuid 0x801f eax - set above */ + if (maxe >= 0x801f) + { + ftcprint (features2, 3, "sev_es"); /* AMD SEV encrypted state */ + } + /* cpuid 0x0007 ebx */ if (maxf >= 0x0007) { @@ -1579,6 +1586,7 @@ format_proc_cpuinfo (void *, char *) ftcprint (features1, 8, "avx512_vp2intersect"); /* vec intcpt d/q */ ftcprint (features1, 10, "md_clear");/* verw clear buf */ ftcprint (features1, 14, "serialize"); /* SERIALIZE instruction */ + ftcprint (features1, 16, "tsxldtrk"); /* TSX Susp Ld Addr Track */ ftcprint (features1, 18, "pconfig"); /* platform config */ ftcprint (features1, 19, "arch_lbr");/* last branch records */ ftcprint (features1, 28, "flush_l1d"); /* flush l1d cache */ Pushed with a trivial change (added a period at the end of the commit message). Thanks. Ken
Re: [PATCH] winsup/doc/faq-what.xml: FAQ 1.2 Windows versions supported
On 9/17/2020 2:29 PM, Brian Inglis wrote: Based on thread https://cygwin.com/pipermail/cygwin/2020-September/246318.html enumerate Vista, 7, 8, 10 progression to be clear, and earliest server 2008 --- winsup/doc/faq-what.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml index ea8496ccbc65..09747532c2e8 100644 --- a/winsup/doc/faq-what.xml +++ b/winsup/doc/faq-what.xml @@ -30,9 +30,9 @@ They can be used from one of the provided Unix shells like bash, tcsh or zsh. What versions of Windows are supported? -Cygwin can be expected to run on all modern, released versions of Windows. -State January 2016 this includes Windows Vista, Windows Server 2008 and all -later versions of Windows up to Windows 10 and Windows Server 2016. +Cygwin can be expected to run on all modern, released versions of Windows, +from Windows Vista, 7, 8, 10, Windows Server 2008, and all +later versions of Windows. The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on released 64 bit versions of Windows, the 64 bit version of course only on 64 bit Windows. Since this is something that changes over time, I don't think you should drop the date completely, though I see no reason to retain "January 2016". What would you think of revising your patch so that the text says something like this: "Cygwin can be expected to run on all modern, released versions of Windows. As of September 2020 this includes Windows Vista, 7, 8, 8.1, and 10, Windows Server 2008, and all later versions of Windows Server." Ken
[PATCH] fhandler_proc.cc(format_proc_cpuinfo): add tsxldtrk, sev_es flags
Add linux-next cpuinfo flags for Intel TSX suspend load address tracking instructions and AMD Secure Encrypted Virtualization with Encrypted State --- winsup/cygwin/fhandler_proc.cc | 8 1 file changed, 8 insertions(+) diff --git a/winsup/cygwin/fhandler_proc.cc b/winsup/cygwin/fhandler_proc.cc index 196bafd18993..6f6e8291a0ca 100644 --- a/winsup/cygwin/fhandler_proc.cc +++ b/winsup/cygwin/fhandler_proc.cc @@ -1376,6 +1376,7 @@ format_proc_cpuinfo (void *, char *) cpuid (, , , , 0x801f); ftcprint (features2, 1, "sev"); /* secure encrypted virt */ + /*ftcprint (features2, 3, "sev_es"); - print below */ } /* cpuid 0x8008 ebx */ if (maxe >= 0x8008) @@ -1400,6 +1401,12 @@ format_proc_cpuinfo (void *, char *) /* ftcprint (features1, 26, "ssb_no"); *//* ssb fixed in hardware */ } + /* cpuid 0x801f eax - set above */ + if (maxe >= 0x801f) + { + ftcprint (features2, 3, "sev_es"); /* AMD SEV encrypted state */ + } + /* cpuid 0x0007 ebx */ if (maxf >= 0x0007) { @@ -1579,6 +1586,7 @@ format_proc_cpuinfo (void *, char *) ftcprint (features1, 8, "avx512_vp2intersect"); /* vec intcpt d/q */ ftcprint (features1, 10, "md_clear");/* verw clear buf */ ftcprint (features1, 14, "serialize"); /* SERIALIZE instruction */ + ftcprint (features1, 16, "tsxldtrk"); /* TSX Susp Ld Addr Track */ ftcprint (features1, 18, "pconfig");/* platform config */ ftcprint (features1, 19, "arch_lbr"); /* last branch records */ ftcprint (features1, 28, "flush_l1d"); /* flush l1d cache */ -- 2.28.0
[PATCH] winsup/doc/faq-what.xml: FAQ 1.2 Windows versions supported
Based on thread https://cygwin.com/pipermail/cygwin/2020-September/246318.html enumerate Vista, 7, 8, 10 progression to be clear, and earliest server 2008 --- winsup/doc/faq-what.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml index ea8496ccbc65..09747532c2e8 100644 --- a/winsup/doc/faq-what.xml +++ b/winsup/doc/faq-what.xml @@ -30,9 +30,9 @@ They can be used from one of the provided Unix shells like bash, tcsh or zsh. What versions of Windows are supported? -Cygwin can be expected to run on all modern, released versions of Windows. -State January 2016 this includes Windows Vista, Windows Server 2008 and all -later versions of Windows up to Windows 10 and Windows Server 2016. +Cygwin can be expected to run on all modern, released versions of Windows, +from Windows Vista, 7, 8, 10, Windows Server 2008, and all +later versions of Windows. The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on released 64 bit versions of Windows, the 64 bit version of course only on 64 bit Windows. -- 2.28.0