From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] pc: memhp: enforce minimal 128Mb alignment for pc-dimm
Date: Tue, 27 Oct 2015 10:31:21 +0200 [thread overview]
Message-ID: <20151027084706-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20151026142432.4a8ca282@nial.brq.redhat.com>
On Mon, Oct 26, 2015 at 02:24:32PM +0100, Igor Mammedov wrote:
> Yep it's workaround but it works around QEMU's broken virtio
> implementation in a simple way without need for guest side changes.
>
> Without foreseeable virtio fix it makes memory hotplug unusable and even
> more so if there were a virtio fix it won't fix old guests since you've
> said that virtio fix would require changes of both QEMU and guest sides.
What makes it not foreseeable?
Apparently only the fact that we have a work-around in place so no one
works on it. I can code it up pretty quickly, but I'm flat out of time
for testing as I'm going on vacation soon, and hard freeze is pretty
close.
GPA space is kind of cheap, but wasting it in chunks of 512M
seems way too aggressive.
--
MST
next prev parent reply other threads:[~2015-10-27 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 9:46 [Qemu-devel] [PATCH v2] pc: memhp: enforce minimal 128Mb alignment for pc-dimm Igor Mammedov
2015-10-26 10:28 ` Michael S. Tsirkin
2015-10-26 13:24 ` Igor Mammedov
2015-10-26 18:42 ` Andrey Korolyov
2015-10-27 7:39 ` Igor Mammedov
2015-10-27 8:31 ` Michael S. Tsirkin [this message]
2015-10-27 8:48 ` Igor Mammedov
2015-10-27 8:53 ` Michael S. Tsirkin
2015-10-27 9:14 ` Igor Mammedov
2015-10-27 16:36 ` Eduardo Habkost
2015-10-29 13:36 ` Igor Mammedov
2015-10-29 18:16 ` [Qemu-devel] RAM backend and guest ABI (was Re: [PATCH v2] pc: memhp: enforce minimal 128Mb) " Eduardo Habkost
2015-10-30 13:07 ` 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=20151027084706-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@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 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).