All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>,
	Ian Jackson <ian.jackson@citrix.com>
Subject: tools: any user of xc_dom_image->allocate?
Date: Fri, 11 Sep 2015 09:25:09 +0200	[thread overview]
Message-ID: <55F281D5.2000609@suse.com> (raw)

While testing xen tools patches to start a pv-domU >512GB I stumbled
over a problem in the domain builder: it is keeping track of the last
allocated virtual address in the memory image it is creating. For
very huge domains (>1TB) this virtual address will wrap around as it is
starting at -2GB and the p2m for such a domain is >2GB.

With a modern pvops kernel (4.3) this would be no problem, as it is
supporting mapping the p2m to an arbitrary address.

In the domain builder, however, I can't currently just ignore the wrap,
as after each memory allocation for the domain image dom->allocate() is
being called with the last allocated virtual address as an argument.
dom->allocate() is allowed to be NULL (in which case it isn't called).

I have found no user of dom->allocate(), deleting it from the struct
xc_dom_image and removing the call sites in xc_dom_core.c didn't break
the build.

Are there any objections to remove the allocate() function in struct
xc_dom_image?


Juergen

             reply	other threads:[~2015-09-11  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11  7:25 Juergen Gross [this message]
2015-09-11 13:25 ` tools: any user of xc_dom_image->allocate? Andrew Cooper

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=55F281D5.2000609@suse.com \
    --to=jgross@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=xen-devel@lists.xen.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 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.