All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "dcm@mccr.org" <dcm@mccr.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: ABI/API breakage
Date: Mon, 20 Jul 2009 16:37:39 +0200	[thread overview]
Message-ID: <200907201637.40053.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C68A3A93.FE92%keir.fraser@eu.citrix.com>

On Monday 20 July 2009 16:15:31 Keir Fraser wrote:
> On 20/07/2009 13:44, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> > Hi!
> >
> > Changeset 19639 changed the ABI/API w/o taking care about backward
> > compatibility.
> > This breaks the xen build in upstream qemu in file hw/xen_domainbuild.c
>
> Is xc_linux_build() the only problematic function? That one could be
> reverted easily enough. Actually superpages should really just get bunged
> in 'struct xc_dom_image' I think. Then the interface for all domain builder
> functions reverts to what it was previously.

For qemu, xc_linux_build() is the only one problematic function.
From the engineering point-of-view, your proposal to collapse superpages
into 'struct xc_dom_image' is the best solution.

Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2009-07-20 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 12:44 ABI/API breakage Christoph Egger
2009-07-20 14:15 ` Keir Fraser
2009-07-20 14:37   ` Christoph Egger [this message]
2009-07-20 14:49     ` Keir Fraser
2009-07-20 15:56       ` Christoph Egger

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=200907201637.40053.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=dcm@mccr.org \
    --cc=keir.fraser@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 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.