From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Re: xenpm: provide core/package cstate residencies
Date: Tue, 13 Jul 2010 08:55:35 +0100 [thread overview]
Message-ID: <C861DA87.1A79C%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C3C3268020000780000AE72@vpn.id2.novell.com>
On 13/07/2010 08:31, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> On 12.07.10 at 19:34, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
>> I applied the hypervisor component of this patch. I leave it to Ian Jackson
>> to deal with the tools part. In future please split patches that touch both
>> hypervisor and tools into a patch series in which each component patch
>> touches only one or the other.
>
> Hmm, is that really a good mechanism, especially when a change
> modifies the hypervisor <-> tools interface in an incompatible way?
> The resulting inconsistency, besides being bad by itself, would likely
> make bisecting more difficult.
In this case the change isn't an API, or even an ABI, breakage. A consistent
build of hypervisor and tools will work, and continue to work, across the
hypervisor-only changeset.
I think there will rarely be interface-breaking patches. If there are we
might have to consider them as one unit. We'll see. A patch series will
usually be the correct way to go however.
-- Keir
prev parent reply other threads:[~2010-07-13 7:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 11:03 xenpm: provide core/package cstate residencies Wei, Gang
2010-07-12 11:26 ` Jan Beulich
2010-07-12 15:11 ` Wei, Gang
2010-07-12 15:22 ` Wei, Gang
2010-07-12 17:34 ` Keir Fraser
2010-07-13 0:36 ` Wei, Gang
2010-07-13 1:09 ` Wei, Gang
2010-07-13 18:42 ` Ian Jackson
2010-07-14 0:17 ` Wei, Gang
2010-07-13 7:31 ` Jan Beulich
2010-07-13 7:55 ` Keir Fraser [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=C861DA87.1A79C%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@novell.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).