From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 2/2] x86: zImage: Propagate acpi_rsdp_addr to kernel via boot parameters
Date: Mon, 18 Jun 2018 12:22:19 +0300 [thread overview]
Message-ID: <dfb5d090ac78e08918f3e0e9df589e508cbc2c58.camel@linux.intel.com> (raw)
In-Reply-To: <CAEUhbmWoqVGvg7TOGpCMFW7iyOG2PLUUyA39eb1mxRvRUOY=dA@mail.gmail.com>
On Sun, 2018-06-17 at 07:22 +0800, Bin Meng wrote:
> Hi Andy,
>
> On Fri, Jan 12, 2018 at 9:01 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Fri, 2018-01-12 at 17:00 +0800, Bin Meng wrote:
> > > Hi Andy,
> > >
> > > On Thu, Jan 11, 2018 at 1:40 AM, Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > New field acpi_rsdp_addr, which has been introduced in boot
> > > > protocol
> > > > v2.14 [1], in boot parameters tells kernel the exact address of
> > > > RDSP
> > > > ACPI table. Knowing it increases robustness of the kernel by
> > > > avoiding
> > > > in some cases traversal through a part of physical memory.
> > > > It will slightly reduce boot time by the same reason.
> > > >
> > > > [1] See Linux kernel commit
> > > >
> > > > 2f74cbf947f4 ("x86/boot: Add the ACPI RSDP address to struct
> > > > setup_header::acpi_rdsp_addr")
> > >
> > > I don't see this commit id in my linux tree. Is this in some
> > > custodian's tree?
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?
> > id=2
> > f74cbf947f45fa082dda8eac1a1f1299a372f49
> >
>
> I checked Linux kernel tree, seems the patch of adding acpi_rdsp_addr
> to setup_header was never accepted. Can you please double check, to
> see whether we still need this in U-Boot?
>
> I built a v4.17 kernel, and the boot protocol is still 2.13.
Indeed. There were a discussion to not apply it for now.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-06-18 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 17:40 [U-Boot] [PATCH v1 1/2] x86: zImage: Move subarch assignment out of cmd_line check Andy Shevchenko
2018-01-10 17:40 ` [U-Boot] [PATCH v1 2/2] x86: zImage: Propagate acpi_rsdp_addr to kernel via boot parameters Andy Shevchenko
2018-01-12 9:00 ` Bin Meng
2018-01-12 13:01 ` Andy Shevchenko
2018-01-15 2:33 ` Bin Meng
2018-01-30 12:50 ` Bin Meng
2018-06-16 23:22 ` Bin Meng
2018-06-18 9:22 ` Andy Shevchenko [this message]
2018-06-18 13:03 ` Bin Meng
2018-06-18 13:27 ` Andy Shevchenko
2018-06-18 13:52 ` Andy Shevchenko
2018-08-22 9:05 ` Bin Meng
2018-08-22 10:23 ` Andy Shevchenko
2018-01-12 9:00 ` [U-Boot] [PATCH v1 1/2] x86: zImage: Move subarch assignment out of cmd_line check Bin Meng
2018-01-15 2:33 ` Bin Meng
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=dfb5d090ac78e08918f3e0e9df589e508cbc2c58.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=u-boot@lists.denx.de \
/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