From: Laszlo Ersek <lersek@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
"Michael S. Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Cc: Aleksei Kovura <alex3kov@zoho.com>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
Steven Newbury <steve@snewbury.org.uk>,
"Richard W.M. Jones" <rjones@redhat.com>,
qemu-devel@nongnu.org, Shannon Zhao <zhaoshenglong@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/4] set the OEM fields in the RSDT and the FADT from the SLIC
Date: Wed, 3 Feb 2016 20:45:59 +0100 [thread overview]
Message-ID: <56B258F7.8090207@redhat.com> (raw)
In-Reply-To: <56B24ED0.8050304@msgid.tls.msk.ru>
On 02/03/16 20:02, Michael Tokarev wrote:
> 03.02.2016 21:51, Laszlo Ersek wrote:
>> Ping #2.
>
> I think I asked this before, but somehow I don't see anyone
> answered. Is this thing worth to have now, when windows7 is
> 2 releases away, everyone is moving to windows8 or 10 rapidly,
> and these OSes don't benefit from this patch due to different
> activation scheme and different licensing terms?
>
> Is it useful for anything but win7 (or 2008) ?
>
> It was definitely useful when I dealt with this issue back
> when win7 come out, at that time it received no interest.
> Now, I think, it is of very limited/questionable use...
I can forward the arguments of the people who requested this functionality:
(1) Aleksei requested this fairly recently:
<https://github.com/tianocore/edk2/issues/5>.
(2) I've seen arguments about the long-term relevance of
Windows 2008 R2:
<https://bugzilla.redhat.com/show_bug.cgi?id=1248758#c15>
and of Windows 7:
<https://bugzilla.redhat.com/show_bug.cgi?id=1248758#c16>
My own arguments:
- SLIC is actually governed by a public Microsoft spec, so it doesn't
hurt to conform to it.
- We went to *much* greater lengths for enabling UEFI Windows 7 / UEFI
Windows Server 2008 R2 on top of OVMF *without* a CSM. UEFI is not
relevant at all in this thread, I'm just saying that in comparison to
what we had taken on for the Win7 family's sake, this effort is almost
negligible.
Thanks
Laszlo
next prev parent reply other threads:[~2016-02-03 19:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 14:12 [Qemu-devel] [PATCH v2 0/4] set the OEM fields in the RSDT and the FADT from the SLIC Laszlo Ersek
2016-01-18 14:12 ` [Qemu-devel] [PATCH v2 1/4] acpi: take oem_id in build_header(), optionally Laszlo Ersek
2016-01-19 3:27 ` Shannon Zhao
2016-01-18 14:12 ` [Qemu-devel] [PATCH v2 2/4] acpi: expose oem_id and oem_table_id in build_rsdt() Laszlo Ersek
2016-01-19 3:29 ` Shannon Zhao
2016-01-18 14:12 ` [Qemu-devel] [PATCH v2 3/4] acpi: add function to extract oem_id and oem_table_id from the user's SLIC Laszlo Ersek
2016-01-18 14:12 ` [Qemu-devel] [PATCH v2 4/4] pc: set the OEM fields in the RSDT and the FADT from the SLIC Laszlo Ersek
2016-01-19 7:35 ` [Qemu-devel] [PATCH v2 0/4] " Steven Newbury
2016-01-19 7:40 ` Steven Newbury
2016-01-27 18:31 ` Laszlo Ersek
2016-02-03 18:51 ` Laszlo Ersek
2016-02-03 19:02 ` Michael Tokarev
2016-02-03 19:45 ` Laszlo Ersek [this message]
2016-02-03 20:37 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B258F7.8090207@redhat.com \
--to=lersek@redhat.com \
--cc=alex3kov@zoho.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=steve@snewbury.org.uk \
--cc=zhaoshenglong@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).