From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
imammedo@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/8] pc: resizeable ROM blocks
Date: Wed, 7 Jan 2015 12:03:13 +0200 [thread overview]
Message-ID: <20150107100313.GC24828@redhat.com> (raw)
In-Reply-To: <54ACE133.4080208@redhat.com>
On Wed, Jan 07, 2015 at 08:33:07AM +0100, Paolo Bonzini wrote:
>
>
> On 24/12/2014 13:41, Michael S. Tsirkin wrote:
> >> I don't think these are necessary, and I thought these were just RFC
> >> when they were posted. I and mst didn't really understand each other,
> >> and I take the fault for not reviewing the submission; however, Peter,
> >> please hold these for a little more.
> >>
> >> Paolo
> >
> > Yes, please do, I'd like Paolo to review at least the memory core
> > changes.
>
> I don't have any issue with the implementation; I'm just not sure that
> this is necessary.
>
> My point is that until ACPI tables are actually trimmed, migration
> really won't be broken. So there is no need to apply these patches
> until/unless we are ready to trim the tables.
So far, the only case where we *didn't* break migration was when
we only did minor changes, in 2.2.
So sorry, I don't buy the "reviewed the code and it's safe" argument.
There's just too much state. Assume there will be bugs. What is a
solution you propose to make at least one way migration work in case of
bugs?
Without answering this question, I don't see how we can make
major changes in the subsystem.
I guess this boils down to this: what's the risk associated with
merging this patchset? It's a small amount of code.
--
MST
next prev parent reply other threads:[~2015-01-07 13:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 11:51 [Qemu-devel] [PULL 0/8] pc: resizeable ROM blocks Michael S. Tsirkin
2014-12-24 11:51 ` [Qemu-devel] [PULL 1/8] cpu: add cpu_physical_memory_clear_dirty_range_nocode Michael S. Tsirkin
2015-01-07 7:16 ` Paolo Bonzini
2014-12-24 11:51 ` [Qemu-devel] [PULL 2/8] memory: add memory_region_set_size Michael S. Tsirkin
2014-12-24 11:51 ` [Qemu-devel] [PULL 3/8] exec: cpu_physical_memory_set/clear_dirty_range Michael S. Tsirkin
2014-12-24 11:51 ` [Qemu-devel] [PULL 4/8] exec: split length -> used_length/max_length Michael S. Tsirkin
2014-12-24 11:51 ` [Qemu-devel] [PULL 5/8] exec: qemu_ram_alloc_resizeable, qemu_ram_resize Michael S. Tsirkin
2015-01-07 7:18 ` Paolo Bonzini
2015-01-07 9:55 ` Michael S. Tsirkin
2014-12-24 11:51 ` [Qemu-devel] [PULL 6/8] arch_init: support resizing on incoming migration Michael S. Tsirkin
2014-12-24 11:51 ` [Qemu-devel] [PULL 7/8] memory: API to allocate resizeable RAM MR Michael S. Tsirkin
2014-12-24 11:51 ` [Qemu-devel] [PULL 8/8] acpi-build: make ROMs RAM blocks resizeable Michael S. Tsirkin
2014-12-30 13:47 ` Marcel Apfelbaum
2014-12-24 12:25 ` [Qemu-devel] [PULL 0/8] pc: resizeable ROM blocks Paolo Bonzini
2014-12-24 12:40 ` Peter Maydell
2014-12-24 12:41 ` Michael S. Tsirkin
2015-01-07 7:33 ` Paolo Bonzini
2015-01-07 10:03 ` Michael S. Tsirkin [this message]
2015-01-07 10:52 ` Paolo Bonzini
2015-01-07 12:37 ` Michael S. Tsirkin
2015-01-07 12:59 ` Paolo Bonzini
2015-01-19 14:04 ` 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=20150107100313.GC24828@redhat.com \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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.