qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Li Zhijian <lizhijian@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, Li Zhijian <zhijianx.li@intel.com>,
	Philip Li <philip.li@intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2 5/5] x86: allow load initrd below 4G for recent linux
Date: Fri, 30 Nov 2018 09:53:23 -0500	[thread overview]
Message-ID: <20181130090249-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1542765966-20244-6-git-send-email-lizhijian@cn.fujitsu.com>

On Wed, Nov 21, 2018 at 10:06:06AM +0800, Li Zhijian wrote:
> a new field xloadflags was added to recent x86 linux, and BIT 1:
> XLF_CAN_BE_LOADED_ABOVE_4G is used to tell bootload that where initrd can be
> loaded saftly.

safely

> 
> Current QEMU always load

loads

> initrd below below_4g_mem_size which

is

> always
> less than 4G, so here limit


limiting

> initrd_max to 4G - 1 simply is enough if
> this bit is set.
> 
> CC: Paolo Bonzini <pbonzini@redhat.com>
> CC: Richard Henderson <rth@twiddle.net>
> CC: Eduardo Habkost <ehabkost@redhat.com>
> CC: "Michael S. Tsirkin" <mst@redhat.com>
> CC: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> ---
>  hw/i386/pc.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
> index 2ffe6fb..6d4b973 100644
> --- a/hw/i386/pc.c
> +++ b/hw/i386/pc.c
> @@ -92,6 +92,7 @@
>  #define FW_CFG_HPET (FW_CFG_ARCH_LOCAL + 4)
>  
>  #define E820_NR_ENTRIES		16
> +#define XLF_CAN_BE_LOADED_ABOVE_4G_MASK (1 << 1)

why not XLF_CAN_BE_LOADED_ABOVE_4G to be consistent
with Linux?
In fact let's import include/uapi/asm/bootparam.h
into standard-headers, and use the macro from there?


>  
>  struct e820_entry {
>      uint64_t address;
> @@ -916,6 +917,17 @@ static void load_linux(PCMachineState *pcms,
>      } else {
>          initrd_max = 0x37ffffff;
>      }
> +    if (protocol >= 0x20c) {

Let's move it above so we have

if (protocol >= 20c)
else if 0x203
else


> +        unsigned int xloadflags = lduw_p(header+0x236);
> +        if (xloadflags & XLF_CAN_BE_LOADED_ABOVE_4G_MASK) {
> +                /*
> +                 * Although kernel allow

allows

> initrd loading to above 4G, here we
> +                 * limit initrd_max to 4G -1


Well not really, it just makes it as large as possible
while still staying below 4G.

> due to

since

> current QEMU always loads
> +                 * initrd

It's not QEMU, is it? It's actually the bios ...

> below pcms->below_4g_mem_size
> +                 */
> +                initrd_max = UINT32_MAX;
> +        }
> +    }
>  
>      if (initrd_max >= pcms->below_4g_mem_size - pcmc->acpi_data_size) {
>          initrd_max = pcms->below_4g_mem_size - pcmc->acpi_data_size - 1;
> -- 
> 2.7.4

  reply	other threads:[~2018-11-30 14:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21  2:06 [Qemu-devel] [PATCH v2 0/5] support loading initrd below 4G for recent kernel Li Zhijian
2018-11-21  2:06 ` [Qemu-devel] [PATCH v2 1/5] unify len and addr type for memory/address APIs Li Zhijian
2018-11-21  2:06   ` [Qemu-devel] [PATCH v2 2/5] change load_image() reture type to ssize_t Li Zhijian
2018-11-21  2:06     ` [Qemu-devel] [PATCH v2 3/5] refactor load_image/load_image_size Li Zhijian
2018-11-21  2:06       ` [Qemu-devel] [PATCH v2 4/5] x86: exit qemu if load_image fails Li Zhijian
2018-11-21  2:06         ` [Qemu-devel] [PATCH v2 5/5] x86: allow load initrd below 4G for recent linux Li Zhijian
2018-11-30 14:53           ` Michael S. Tsirkin [this message]
2018-12-03  6:12             ` Li Zhijian
2018-11-30 13:52         ` [Qemu-devel] [PATCH v2 4/5] x86: exit qemu if load_image fails Peter Maydell
2018-11-30 13:47     ` [Qemu-devel] [PATCH v2 2/5] change load_image() reture type to ssize_t Peter Maydell
2018-11-30 15:14       ` Peter Maydell
2018-12-03  6:16         ` Li Zhijian
2018-11-30 13:40   ` [Qemu-devel] [PATCH v2 1/5] unify len and addr type for memory/address APIs Peter Maydell
2018-12-03  6:42     ` Li Zhijian

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=20181130090249-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=philip.li@intel.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=zhijianx.li@intel.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).