All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Keir Fraser <keir@xen.org>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Marcus Granado <Marcus.Granado@eu.citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 3/3] xenoprof: Make the escape code consistent across 32 and 64-bit xen
Date: Mon, 23 Jan 2012 17:40:33 +0000	[thread overview]
Message-ID: <1327340433.26455.338.camel@elijah> (raw)
In-Reply-To: <CB4349F0.37FDB%keir@xen.org>

On Mon, 2012-01-23 at 17:31 +0000, Keir Fraser wrote:
> > I really prefer to keep patches with no functional change separate from
> > those with a pretty major functional change; even if the major
> > functional change is only one line. :-)
> 
> The one-line major functional change didn't work. Obviously the other
> changes to make it build must be part of the same logical patch.

Perhaps "functional" change isn't what I meant, so much as
"guest-visible behavior change".

If I were writing this patch series from the beginning, I'd have one
patch which "fixed" the various internal functions to use 64-bits for
EIP, since even in 32-bit that value in the struct can be 64-bit.  That
patch by itself could have a bug in it, and so as a reviewer /
archaeologist, *I* would have preferred it did just that one thing, so I
didn't have to figure out what each individual line was supposed to be
doing.  Then the guest-visible functional change would have been its own
patch.

In any case, I'll send a combined patch tomorrow, since that seems
preferred.

 -George

  reply	other threads:[~2012-01-23 17:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 18:45 [PATCH 3/3] xenoprof: Make the escape code consistent across 32 and 64-bit xen Marcus Granado
2012-01-23  9:57 ` Jan Beulich
2012-01-23 10:16   ` Ian Campbell
2012-01-23 10:47     ` Jan Beulich
2012-01-23 14:04       ` Jan Beulich
2012-01-23 16:01         ` George Dunlap
2012-01-23 16:30           ` Jan Beulich
2012-01-23 16:51             ` George Dunlap
2012-01-23 17:01               ` Jan Beulich
2012-01-23 17:31               ` Keir Fraser
2012-01-23 17:40                 ` George Dunlap [this message]
2012-01-24  8:50                   ` Jan Beulich

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=1327340433.26455.338.camel@elijah \
    --to=george.dunlap@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Marcus.Granado@eu.citrix.com \
    --cc=keir@xen.org \
    --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.