From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Avi Kivity <avi@redhat.com>
Cc: kvm-ppc@vger.kernel.org, linuxppc-dev@ozlabs.org,
paulus@samba.org, Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org
Subject: Re: [PATCH 07/10] KVM: PPC: Add PAPR hypercall code for PR mode
Date: Tue, 09 Aug 2011 17:02:00 -0500 [thread overview]
Message-ID: <1312927320.29273.19.camel@pasglop> (raw)
In-Reply-To: <4E4167F9.5090305@redhat.com>
On Tue, 2011-08-09 at 20:01 +0300, Avi Kivity wrote:
> On 08/09/2011 07:51 PM, Alexander Graf wrote:
> >> Just put your own (or your employers'). If someone contributed to
> >> the code they can add their copyrights (or ask you do do it before
> >> inclusion).
> >>
> >> It would be good to get Paul's or Ben's so that the unimportant
> >> characters between the whitespace get some braintime.
> >
> >
> > So you mean I just put both copyright statements there? That's a nice
> > idea!
> >
> >
>
> I meant Paul's or Ben's *review*.
Ben's currently travelling doing some bringup :-) I will try to have a
look but I can't promise anything for the next 2 weeks.
Cheers,
Ben.
next prev parent reply other threads:[~2011-08-09 22:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 16:31 [PATCH 00/10] PAPR virtualization on PR KVM Alexander Graf
2011-08-09 16:31 ` [PATCH 01/10] KVM: PPC: move compute_tlbie_rb to book3s common header Alexander Graf
2011-11-08 17:08 ` [PATCH] KVM: PPC: move compute_tlbie_rb to book3s_64 " Andreas Schwab
2011-11-11 16:03 ` Alexander Graf
2011-08-09 16:31 ` [PATCH 02/10] KVM: PPC: Add papr_enabled flag Alexander Graf
2011-08-09 16:31 ` [PATCH 03/10] KVM: PPC: Check privilege level on SPRs Alexander Graf
2011-08-09 16:31 ` [PATCH 04/10] KVM: PPC: Interpret SDR1 as HVA in PAPR mode Alexander Graf
2011-08-09 16:31 ` [PATCH 05/10] KVM: PPC: Read out syscall instruction on trap Alexander Graf
2011-08-09 16:31 ` [PATCH 06/10] KVM: PPC: Add support for explicit HIOR setting Alexander Graf
2011-08-09 16:31 ` [PATCH 07/10] KVM: PPC: Add PAPR hypercall code for PR mode Alexander Graf
2011-08-09 16:40 ` Avi Kivity
2011-08-09 16:46 ` Alexander Graf
2011-08-09 16:49 ` Avi Kivity
2011-08-09 16:51 ` Alexander Graf
2011-08-09 17:01 ` Avi Kivity
2011-08-09 22:02 ` Benjamin Herrenschmidt [this message]
2011-08-12 3:35 ` David Gibson
2011-08-12 5:38 ` Alexander Graf
2011-08-12 7:43 ` David Gibson
2011-08-12 8:09 ` Alexander Graf
2011-08-09 16:31 ` [PATCH 08/10] KVM: PPC: Stub emulate CFAR and PURR SPRs Alexander Graf
2011-08-09 16:31 ` [PATCH 09/10] KVM: PPC: Support SC1 hypercalls for PAPR in PR mode Alexander Graf
2011-08-12 3:33 ` David Gibson
2011-08-12 5:35 ` Alexander Graf
2011-08-12 7:43 ` David Gibson
2011-08-12 8:07 ` Alexander Graf
2011-11-08 17:17 ` [PATCH] KVM: PPC: protect use of kvmppc_h_pr Andreas Schwab
2011-11-11 16:03 ` Alexander Graf
2011-08-09 16:31 ` [PATCH 10/10] KVM: PPC: Enable the PAPR CAP for Book3S Alexander Graf
2011-08-10 4:42 ` Paul Mackerras
2011-08-10 7:59 ` Alexander Graf
2011-08-10 12:26 ` Paul Mackerras
2011-08-10 12:29 ` Alexander Graf
2011-08-09 16:42 ` [PATCH 00/10] PAPR virtualization on PR KVM Avi Kivity
2011-08-09 16:49 ` Alexander Graf
2011-08-10 12:31 ` [PATCH 11/10] KVM: PPC: Add sanity checking to vcpu_run 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=1312927320.29273.19.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 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).