From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC 2/3] acpi: load and link tables from /etc/acpi/
Date: Mon, 29 Apr 2013 16:25:13 +0300 [thread overview]
Message-ID: <20130429132513.GB1850@redhat.com> (raw)
In-Reply-To: <517E5C4D.7080502@redhat.com>
On Mon, Apr 29, 2013 at 01:41:01PM +0200, Laszlo Ersek wrote:
> Not sure how much it counts, but I personally can agree with you on this
> direction :)
>
> One note below:
>
> > @@ -603,8 +604,72 @@ acpi_setup(void)
> > if (! CONFIG_ACPI)
> > return;
> >
> > + int acpi_generate = 1;
> > +
> > dprintf(3, "init ACPI tables\n");
> >
> > + struct romfile_s *file = NULL;
> > + for (;;) {
> > + file = romfile_findprefix("/etc/acpi/", file);
> > + if (!file)
> > + break;
> > +
> > + /*
> > + * Disable ACPI table generation. All ACPI tables must come from
> > + * etc/acpi/ romfile entries.
> > + */
> > + acpi_generate = 0;
> > +
>
> [...]
>
> > + }
> > +
> > + linker_link("/etc/linker-script");
> > +
> > + if (!acpi_generate) {
> > + return;
> > + }
> > +
> > + dprintf(3, "generate ACPI tables\n");
> > +
> > // This code is hardcoded for PIIX4 Power Management device.
> > struct pci_device *pci = pci_find_init_device(acpi_find_tbl, NULL);
> > if (!pci)
>
> Are you deliberately calling linker_link() independently from
> "acpi_generate"? My hunch is that linker_link() only makes sense if
> acpi_generate == 0 (ie. qemu has passed down at least one table to
> repoint some pointer to), but I may be missing a use case.
>
> Thanks
> Laszlo
In theory linker code is unrelated to acpi, and host
can the linker to patch any romfile.
I could add if (!acpi_generate) but it just seems
like adding code to remove something potentially useful.
--
MST
next prev parent reply other threads:[~2013-04-29 13:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 9:02 [Qemu-devel] [PATCH RFC 0/3] seabios: move acpi table formatting out of bios Michael S. Tsirkin
2013-04-25 9:02 ` [Qemu-devel] [PATCH RFC 1/3] linker: utility to patch in-memory ROM files Michael S. Tsirkin
2013-04-25 9:02 ` [Qemu-devel] [PATCH RFC 2/3] acpi: load and link tables from /etc/acpi/ Michael S. Tsirkin
2013-04-29 11:41 ` Laszlo Ersek
2013-04-29 13:25 ` Michael S. Tsirkin [this message]
2013-04-25 9:02 ` [Qemu-devel] [PATCH RFC 3/3] acpi: add an option to disable builtin tables Michael S. Tsirkin
2013-04-25 18:19 ` [Qemu-devel] [SeaBIOS] [PATCH RFC 0/3] seabios: move acpi table formatting out of bios Fred .
2013-04-25 21:11 ` Michael S. Tsirkin
2013-04-25 22:39 ` Kevin O'Connor
2013-05-07 18:00 ` [Qemu-devel] " Michael S. Tsirkin
2013-05-07 23:01 ` Kevin O'Connor
2013-05-08 9:31 ` Gleb Natapov
2013-05-08 10:29 ` Michael S. Tsirkin
2013-05-08 10:34 ` Gleb Natapov
2013-05-08 10:43 ` Michael S. Tsirkin
2013-05-08 10:59 ` Gleb Natapov
2013-05-08 11:07 ` Michael S. Tsirkin
2013-05-08 11:35 ` Gleb Natapov
2013-05-08 12:35 ` Michael S. Tsirkin
2013-05-08 12:41 ` Gleb Natapov
2013-05-08 22:55 ` Kevin O'Connor
2013-05-09 5:42 ` Gleb Natapov
2013-05-08 18:15 ` Michael S. Tsirkin
2013-05-09 5:24 ` Gleb Natapov
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=20130429132513.GB1850@redhat.com \
--to=mst@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
/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).