From: Avi Kivity <avi@redhat.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/5] bios: >4G updates
Date: Wed, 24 Sep 2008 14:07:22 +0300 [thread overview]
Message-ID: <48DA1F6A.40105@redhat.com> (raw)
In-Reply-To: <1222188118.8138.101.camel@2710p.home>
Alex Williamson wrote:
> As requested, here's the follow-on to the >4G MTRR changes split into
> functional bits.
>
> [1/5] Rename variables to reflect what they're really reporting
> [2/5] Reformat ram_probe() to match the rest of the code
> [3/5] Add SMBIOS info for memory above 4G
> [4/5] Fix the SMBIOS type 19 & 20 range end address
> [5/5] Optional - switch default MTRR type to WB and only cover MMIO
>
> I've taken some liberties renaming and reformatting, if we'd rather not
> introduce too many extraneous changes, I can drop those. The SMBIOS
> changes seem to work up to 32767MB, then we hit a limitation in the type
> 17 table only providing 15bits for the size. We might need to describe
> multiple virtual DIMMs to get around that, but it's a separate issue.
>
> The final patch is optional and switches over to make the variable MTRRs
> only describe the MMIO hole, leaving the rest of the address space
> default to WB. I can't say I fully understand the implications of
> hotplug memory for this scenario. Let me know if there are comments.
>
The patches all look good, however renaming and reformatting will lead
to merge headaches later on. We haven't been good at working with bochs
bios upstream.
Can you peek in bochs upstream and see if it's worth merging? If not,
I'll just merge these patches.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-09-24 11:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 16:41 [PATCH 0/5] bios: >4G updates Alex Williamson
2008-09-24 11:07 ` Avi Kivity [this message]
2008-09-24 16:17 ` Alex Williamson
2008-09-25 16:08 ` Alex Williamson
2008-09-28 15:19 ` Avi Kivity
2008-09-30 13:31 ` Avi Kivity
2008-09-30 16:46 ` Avi Kivity
2008-09-30 21:19 ` Alex Williamson
2008-10-02 12:33 ` Avi Kivity
2008-10-12 22:50 ` Kevin O'Connor
2008-10-13 6:45 ` Gleb Natapov
2008-10-14 15:29 ` Avi Kivity
2008-10-14 16:00 ` Anthony Liguori
2008-10-14 16:17 ` Avi Kivity
2008-10-14 16:21 ` Glauber Costa
2008-10-15 0:41 ` Kevin O'Connor
2008-10-15 17:46 ` Avi Kivity
2008-10-16 0:31 ` Kevin O'Connor
2008-10-13 16:33 ` Alex Williamson
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=48DA1F6A.40105@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@hp.com \
--cc=kvm@vger.kernel.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).