qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: peter.maydell@linaro.org, ehabkost@redhat.com,
	imammedo@redhat.com, qemu-devel@nongnu.org,
	"Richard W.M. Jones" <rjones@redhat.com>,
	zhaoshenglong@huawei.com, pbonzini@redhat.com,
	Laszlo Ersek <lersek@redhat.com>,
	rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 1/2] acpi: Allow ACPI default OEM ID and OEM table ID fields to be set.
Date: Thu, 3 Sep 2015 22:56:22 +0300	[thread overview]
Message-ID: <20150903225605-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <55E8764D.6020302@msgid.tls.msk.ru>

On Thu, Sep 03, 2015 at 07:33:17PM +0300, Michael Tokarev wrote:
> 03.09.2015 18:37, Laszlo Ersek wrote:
> []
> > Actually, 6 + 4 + 4 = 14, so OemID and OemTableID. But, you are right, I
> > was working off the commit message & comments only, not the actual
> > amount of bytes copied.
> > 
> > This ties down both OemID and OemTableId, between all of RSDT, SLIC, and
> > FADT. Since
> > - I argue against exposing a generic oem_table_id on the command
> >   line (unlike oem_id),
> > - and I also find that an oem_table_id "map" would be overkill,
> > 
> > I think it follows that I can only ask for the special SLIC-handling
> > logic already visible in your patch. "User passed in SLIC --> adapt RSDT
> > and FADT." That is, it is already user-controlled.
> 
> It might be useful to have it controllable by user in other cases too.
> But I don't have any usage case for that.
> 
> > (The FADT change will ensure that OVMF will update the RSDT that *it*
> > installs.)
> > 
> > This is just my preference, of course... But at least it doesn't seem to
> > conflict with Michael's! :)
> 
> Yes, it might just work. Especially since in case when SLIC is specified,
> the oem_table&Co should come from SLIC, not forcing user to specify them
> on command line.  Command line can be used anyway, with the default value
> coming from slic if it is provided.
> 
> BTW, I updated the patch for 2.4 a few days ago, it is hackish as I wanted
> to touch as few files as possible.
> 
> And BTW2, the code in acpi/core.c uses its own local definition of ACPI
> table data structures, instead of using common code from acpi.h... ;)
> 
> Thanks,
> 
> /mjt

Yes, we want that cleaned up.

  parent reply	other threads:[~2015-09-03 19:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 19:03 [Qemu-devel] [PATCH 1/2] acpi: Allow ACPI default OEM ID and OEM table ID fields to be set Richard W.M. Jones
2015-09-02 19:03 ` Richard W.M. Jones
2015-09-02 19:16   ` Richard W.M. Jones
2015-09-02 21:32   ` Michael S. Tsirkin
2015-09-03 15:09     ` Laszlo Ersek
2015-09-03 15:17       ` Michael Tokarev
2015-09-03 15:37         ` Laszlo Ersek
2015-09-03 16:33           ` Michael Tokarev
2015-09-03 16:44             ` Laszlo Ersek
2015-09-03 19:56             ` Michael S. Tsirkin [this message]
2015-09-03 19:55           ` Michael S. Tsirkin
2015-09-03 20:51             ` Richard W.M. Jones
2015-09-02 19:03 ` [Qemu-devel] [PATCH 2/2] acpi: Remove unused definition 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=20150903225605-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=rth@twiddle.net \
    --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).