qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Don Slutz <dslutz@verizon.com>
Cc: "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
	xen-devel@lists.xensource.com,
	"Andreas Färber" <afaerber@suse.de>,
	"Anthony Liguori" <aliguori@amazon.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/4] Add max-ram-below-4g (was Add pci_hole_min_size machine option)
Date: Mon, 5 May 2014 11:12:57 +0300	[thread overview]
Message-ID: <20140505081257.GA12228@redhat.com> (raw)
In-Reply-To: <53569954.9040807@terremark.com>

On Tue, Apr 22, 2014 at 12:31:16PM -0400, Don Slutz wrote:
> On 04/18/14 10:10, Andreas Färber wrote:
> >Am 25.03.2014 10:08, schrieb Michael S. Tsirkin:
> >>On Mon, Mar 24, 2014 at 07:55:32PM -0400, Don Slutz wrote:
> >>>Changes v2 to v3:
> >>>   Stefano Stabellini:
> >>>     Acked-by #1 "xen-all: Fix xen_hvm_init() to adjust pc memory"
> >>>     Adjust for code readability #4 "xen-all: Pass max_ram_below_4g to xen_hvm_init."
> >>>        Set max_ram_below_4g always and use it to calculate above_4g_mem_size,
> >>>        below_4g_mem_size.
> >>>
> >>>Changes v1 to v2:
> >>>   Michael S. Tsirkin:
> >>>     Rename option.
> >>>     Only add it to machine types that support it.
> >>>   Split into 4 parts.
> >>>
> >>>1/4 -- xen-all: Fix xen_hvm_init() to adjust pc memory layout
> >>>
> >>>   This looks to be a possible bug that has yet to be found.
> >>>   below_4g_mem_size and above_4g_mem_size are stored in PcGuestInfo
> >>>   (pc_guest_info_init) which are currently not "correct".  This and
> >>>   4/4 change the same lines.
> >>>
> >>>2/4 -- GlobalProperty: Display warning about unused -global
> >>>
> >>>     My testing showed that setting a global property on an object
> >>>     that is not used is not reported at all.  This is added to help
> >>>     when the new global is set but not used.  The negative not_used
> >>>     was picked so that all static objects are assumed to be used
> >>>     even when they are not.
> >>>
> >>>3/4 -- pc & q35: Add new object pc-memory-layout
> >>>
> >>>   The objects that it might make sense to add this property to all
> >>>   get created too late.  So add a new object just to hold this
> >>>   property.  Name it so that it is expected that only pc (and q35)
> >>>   machine types support it.
> >>>
> >>>4/4 -- xen-all: Pass max_ram_below_4g to xen_hvm_init
> >>>
> >>>   Seprate the xen only part of the change.  Currectly based on patch 1/4
> >>>
> >>>Don Slutz (4):
> >>>   xen-all: Fix xen_hvm_init() to adjust pc memory layout.
> >>>   GlobalProperty: Display warning about unused -global
> >>>   pc & q35: Add new object pc-memory-layout.
> >>>   xen-all: Pass max_ram_below_4g to xen_hvm_init.
> >>>
> >>>  hw/core/qdev-properties-system.c |  1 +
> >>>  hw/core/qdev-properties.c        | 15 ++++++++++++
> >>>  hw/i386/pc.c                     | 42 ++++++++++++++++++++++++++++++++
> >>>  hw/i386/pc_piix.c                | 52 +++++++++++++++++++++++++++-------------
> >>>  hw/i386/pc_q35.c                 | 50 ++++++++++++++++++++++++++------------
> >>>  include/hw/i386/pc.h             |  2 ++
> >>>  include/hw/qdev-core.h           |  1 +
> >>>  include/hw/qdev-properties.h     |  1 +
> >>>  include/hw/xen/xen.h             |  3 ++-
> >>>  vl.c                             |  2 ++
> >>>  xen-all.c                        | 46 +++++++++++++++++++----------------
> >>>  xen-stub.c                       |  3 ++-
> >>>  12 files changed, 165 insertions(+), 53 deletions(-)
> >>Andreas, could you review pls, esp patch 2?
> >Michael, I don't see a dependency of the later patches on 2/4, so I'd
> >like to split that one out of this series and reiterate.
> 
> I am happy to split out 2/4.

I'm waiting for a repost or did I misunderstand?

> >I'll have some minor comments on the rest.
> >
> >Don, in general please do not end subjects with a dot.
> 
> Ok, will attempt to do so.
> 
>    -Don Slutz
> 
> >CC'ing Eduardo and Igor who looked into 4G issues previously.
> >
> >Regards,
> >Andreas
> >

  parent reply	other threads:[~2014-05-05  8:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 23:55 [Qemu-devel] [PATCH v3 0/4] Add max-ram-below-4g (was Add pci_hole_min_size machine option) Don Slutz
2014-03-24 23:55 ` [Qemu-devel] [PATCH v3 1/4] xen-all: Fix xen_hvm_init() to adjust pc memory layout Don Slutz
2014-03-24 23:55 ` [Qemu-devel] [PATCH v3 2/4] GlobalProperty: Display warning about unused -global Don Slutz
2014-03-24 23:55 ` [Qemu-devel] [PATCH v3 3/4] pc & q35: Add new object pc-memory-layout Don Slutz
2014-03-24 23:55 ` [Qemu-devel] [PATCH v3 4/4] xen-all: Pass max_ram_below_4g to xen_hvm_init Don Slutz
2014-03-25 11:17   ` Stefano Stabellini
2014-03-25  9:08 ` [Qemu-devel] [PATCH v3 0/4] Add max-ram-below-4g (was Add pci_hole_min_size machine option) Michael S. Tsirkin
     [not found]   ` <5351324E.9090603@suse.de>
     [not found]     ` <53569954.9040807@terremark.com>
2014-05-05  8:12       ` Michael S. Tsirkin [this message]
2014-05-05 16:16         ` Don Slutz

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=20140505081257.GA12228@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=dslutz@verizon.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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).