From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Ani Sinha <ani@anisinha.ca>,
gsomlo@gmail.com, qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [PATCH v2] hw/smbios: fix memory corruption for large guests due to handle overlap
Date: Fri, 4 Feb 2022 08:51:13 -0500 [thread overview]
Message-ID: <20220204085001-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220204103423.71ec5c6b@redhat.com>
On Fri, Feb 04, 2022 at 10:34:23AM +0100, Igor Mammedov wrote:
> > @@ -982,7 +986,7 @@ void smbios_get_tables(MachineState *ms,
> > uint8_t **anchor, size_t *anchor_len,
> > Error **errp)
> > {
> > - unsigned i, dimm_cnt;
> > + unsigned i, dimm_cnt, offset;
> >
> > if (smbios_legacy) {
> > *tables = *anchor = NULL;
> > @@ -1012,6 +1016,19 @@ void smbios_get_tables(MachineState *ms,
> >
> > dimm_cnt = QEMU_ALIGN_UP(current_machine->ram_size, MAX_DIMM_SZ) / MAX_DIMM_SZ;
>
> Michael, Gerd,
>
> Another question is why we split memory on 16Gb chunks, to begin with.
> Maybe instead of doing so, we should just add 1 type17 entry describing
> whole system RAM size. In which case we don't need this dance around
> handle offsets anymore.
I'm not sure - could be some guests just get confused if a chunk
is too big ... we'd need a lot of testing if we change that ...
--
MST
next prev parent reply other threads:[~2022-02-04 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 13:09 [PATCH v2] hw/smbios: fix memory corruption for large guests due to handle overlap Ani Sinha
2022-02-04 9:34 ` Igor Mammedov
2022-02-04 11:05 ` Gerd Hoffmann
2022-02-04 12:18 ` Igor Mammedov
2022-02-04 13:52 ` Ani Sinha
2022-02-10 12:32 ` Ani Sinha
2022-02-04 13:51 ` Michael S. Tsirkin [this message]
2022-02-07 15:12 ` Ani Sinha
2022-02-08 7:48 ` Igor Mammedov
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=20220204085001-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ani@anisinha.ca \
--cc=gsomlo@gmail.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.