From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Stuart Yoder <stuart.yoder@freescale.com>,
kvm-ppc <kvm-ppc@vger.kernel.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH v11 5/8] KVM: PPC: ev_idle hcall support for e500 guests
Date: Mon, 02 Jul 2012 13:24:21 +0000 [thread overview]
Message-ID: <1341235461.2588.48.camel@pasglop> (raw)
In-Reply-To: <41C7EDF8-59B4-4F03-83AF-9B8561082EFB@suse.de>
On Mon, 2012-07-02 at 14:20 +0200, Alexander Graf wrote:
>
> Ben, would you be opposed to a macro that does this? Open-coding
> subtile details like this always makes me wary we could screw them
> up :)
That's definitely material for a macro (and fixup the gazillion places
where we do it by hand already :-)
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Stuart Yoder <stuart.yoder@freescale.com>,
kvm-ppc <kvm-ppc@vger.kernel.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH v11 5/8] KVM: PPC: ev_idle hcall support for e500 guests
Date: Mon, 02 Jul 2012 23:24:21 +1000 [thread overview]
Message-ID: <1341235461.2588.48.camel@pasglop> (raw)
In-Reply-To: <41C7EDF8-59B4-4F03-83AF-9B8561082EFB@suse.de>
On Mon, 2012-07-02 at 14:20 +0200, Alexander Graf wrote:
>
> Ben, would you be opposed to a macro that does this? Open-coding
> subtile details like this always makes me wary we could screw them
> up :)
That's definitely material for a macro (and fixup the gazillion places
where we do it by hand already :-)
Cheers,
Ben.
next prev parent reply other threads:[~2012-07-02 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 20:04 [PATCH v11 5/8] KVM: PPC: ev_idle hcall support for e500 guests Stuart Yoder
2012-06-22 20:04 ` Stuart Yoder
2012-07-02 12:20 ` Alexander Graf
2012-07-02 12:20 ` Alexander Graf
2012-07-02 13:24 ` Benjamin Herrenschmidt [this message]
2012-07-02 13:24 ` Benjamin Herrenschmidt
2012-07-02 13:40 ` Alexander Graf
2012-07-02 13:40 ` Alexander Graf
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=1341235461.2588.48.camel@pasglop \
--to=benh@au1.ibm.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=stuart.yoder@freescale.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.