qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Juan Quintela <quintela@redhat.com>,
	qemu-devel@nongnu.org, dgilbert@redhat.com,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/8] pc: resizeable ROM blocks
Date: Mon, 19 Jan 2015 15:04:38 +0100	[thread overview]
Message-ID: <20150119150438.5d0b0ab9@nial.brq.redhat.com> (raw)
In-Reply-To: <54ACE133.4080208@redhat.com>

On Wed, 07 Jan 2015 08:33:07 +0100
Paolo Bonzini <pbonzini@redhat.com> 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.

My ACPI patches, mainly do not include any trimming due to the fact that
it will break current migration (i.e. blob size conditions will change
and break currently working setups). With this series we could trim
not present devices descriptions from ACPI tables reducing its size
safely (wrt migration). IMHO this series should be in tree before any
trimming is implemented and the sooner the better (i.e. we would be able
do forward/backward migration to/from 2.3(with theses patches) to/from
newer versions with trimmed tables).

I'm in favor of this series approach as it let us take care of ACPI tables
migration once and don't care about it anymore VS Paolo's byte-by-byte
compatible SSDT for each machine type whenever we change/fix ACPI tables.

> 
> Paolo
> 

      parent reply	other threads:[~2015-01-19 14:04 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
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 [this message]

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=20150119150438.5d0b0ab9@nial.brq.redhat.com \
    --to=imammedo@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=mst@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 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).