From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx2.suse.de", Issuer "CAcert Class 3 Root" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 298ADB723B for ; Wed, 10 Aug 2011 02:52:01 +1000 (EST) Message-ID: <4E4165AB.8030704@suse.de> Date: Tue, 09 Aug 2011 18:51:55 +0200 From: Alexander Graf MIME-Version: 1.0 To: Avi Kivity Subject: Re: [PATCH 07/10] KVM: PPC: Add PAPR hypercall code for PR mode References: <1312907508-14599-1-git-send-email-agraf@suse.de> <1312907508-14599-8-git-send-email-agraf@suse.de> <4E416315.2080800@redhat.com> <4E41646C.1070500@suse.de> <4E41651C.7050709@redhat.com> In-Reply-To: <4E41651C.7050709@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 08/09/2011 06:49 PM, Avi Kivity wrote: > On 08/09/2011 07:46 PM, Alexander Graf wrote: >> On 08/09/2011 06:40 PM, Avi Kivity wrote: >>> On 08/09/2011 07:31 PM, Alexander Graf wrote: >>>> When running a PAPR guest, we need to handle a few hypercalls in >>>> kernel space, >>>> most prominently the page table invalidation (to sync the shadows). >>>> >>>> So this patch adds handling for a few PAPR hypercalls to PR mode >>>> KVM. I tried >>>> to share the code with HV mode, but it ended up being a lot easier >>>> this way >>>> around, as the two differ too much in those details. >>>> >>>> >>>> +++ b/arch/powerpc/kvm/book3s_pr_papr.c >>>> @@ -0,0 +1,158 @@ >>>> +/* >>>> + * Copyright (C) 2011. Freescale Inc. All rights reserved. >>>> + * >>>> + * Authors: >>>> + * Alexander Graf >>>> + * Paul Mackerras >>>> + * >>>> + * Description: >>>> + * >>>> + * Hypercall handling for running PAPR guests in PR KVM on Book 3S >>>> + * processors. >>>> + * >>>> + * This program is free software; you can redistribute it and/or >>>> modify >>>> + * it under the terms of the GNU General Public License, version >>>> 2, as >>>> + * published by the Free Software Foundation. >>>> + */ >>> >>> Copyright freescale, authors Paul and yourself? >> >> Yeah, I'm reasonably clueless when it comes to legal stuff. This code >> is inspired by Paul's, but is mostly rewritten since it's so tied >> into the virtual MMU. What would the copyright be in that case? > > 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! Alex