From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Paul Brook <paul-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: Re: [Qemu-devel] Merging KVM QEMU changes upstream
Date: Fri, 25 Jan 2008 12:50:21 -0600 [thread overview]
Message-ID: <479A2F6D.6010007@codemonkey.ws> (raw)
In-Reply-To: <200801251843.37551.paul-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
Paul Brook wrote:
>> Is this a reasonable merge strategy? We won't introduce regressions but
>> I can't guarantee these new things will work cross-architecture.
>>
>
> I think it depends to some extent whether things will need rewriting to be
> made cross-architecture. In particular if this requires interface changes.
> This means either breaking existing guests, or having to support both
> interfaces.
>
That's a reasonable stance to take. I don't think anything in the tree
right now presents that problem. I'll start sending out some patches
and if you have specific concerns, we can talk about them 1-by-1.
> e.g. the extboot stuff seems like something that should be usable by all
> targets, except that the current interface looks like it's inherently x86
> specific.
>
Well with extboot in particular, the only interface is between the
extboot option ROM and QEMU and I don't think that breaking that
interface will matter much in practice.
Regards,
Anthony Liguori
> Paul
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>, qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] Merging KVM QEMU changes upstream
Date: Fri, 25 Jan 2008 12:50:21 -0600 [thread overview]
Message-ID: <479A2F6D.6010007@codemonkey.ws> (raw)
In-Reply-To: <200801251843.37551.paul@codesourcery.com>
Paul Brook wrote:
>> Is this a reasonable merge strategy? We won't introduce regressions but
>> I can't guarantee these new things will work cross-architecture.
>>
>
> I think it depends to some extent whether things will need rewriting to be
> made cross-architecture. In particular if this requires interface changes.
> This means either breaking existing guests, or having to support both
> interfaces.
>
That's a reasonable stance to take. I don't think anything in the tree
right now presents that problem. I'll start sending out some patches
and if you have specific concerns, we can talk about them 1-by-1.
> e.g. the extboot stuff seems like something that should be usable by all
> targets, except that the current interface looks like it's inherently x86
> specific.
>
Well with extboot in particular, the only interface is between the
extboot option ROM and QEMU and I don't think that breaking that
interface will matter much in practice.
Regards,
Anthony Liguori
> Paul
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
next prev parent reply other threads:[~2008-01-25 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 17:53 Merging KVM QEMU changes upstream Anthony Liguori
2008-01-25 17:53 ` [Qemu-devel] " Anthony Liguori
[not found] ` <479A222E.4-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-25 18:43 ` Paul Brook
2008-01-25 18:43 ` Paul Brook
[not found] ` <200801251843.37551.paul-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
2008-01-25 18:50 ` Anthony Liguori [this message]
2008-01-25 18:50 ` [kvm-devel] " Anthony Liguori
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=479A2F6D.6010007@codemonkey.ws \
--to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=paul-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.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.