From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Date: Sun, 10 Jan 2010 12:37:52 +0000 Subject: Re: [PATCH 1/2] KVM: PPC: Pass through program interrupts Message-Id: <4B49CA20.6000303@redhat.com> List-Id: References: <1263090452-30439-1-git-send-email-agraf@suse.de> <4B49C684.8080407@redhat.com> <3F51B03C-D36B-49F9-9AF3-EF5227DFAE3F@suse.de> In-Reply-To: <3F51B03C-D36B-49F9-9AF3-EF5227DFAE3F-l3A5Bk7waGM@public.gmane.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Alexander Graf Cc: kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kvm-ppc On 01/10/2010 02:32 PM, Alexander Graf wrote: > > >> Applied both, and queued for .33. I was able to guess this from the description, but please mention it explicitly in the future. >> > I'm not sure what to mention. From a stability point of view, all the Book3S patches should go in .33 because they all fix severe bugs. > > But then again the question is what our goal for .33 is. If we only want to give out the message "KVM for Book3S is coming! Stay tuned!" then we shouldn't do any updates for .33. If we want to have something working to the best of our knowledge, all patches should go into .33. > Given the other 9-patch series, I'll regard .33 as a sneak preview (look but don't touch) and .34 will be the first really serious kvm ppc64 release. -- error compiling committee.c: too many arguments to function From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/2] KVM: PPC: Pass through program interrupts Date: Sun, 10 Jan 2010 14:37:52 +0200 Message-ID: <4B49CA20.6000303@redhat.com> References: <1263090452-30439-1-git-send-email-agraf@suse.de> <4B49C684.8080407@redhat.com> <3F51B03C-D36B-49F9-9AF3-EF5227DFAE3F@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kvm-ppc To: Alexander Graf Return-path: In-Reply-To: <3F51B03C-D36B-49F9-9AF3-EF5227DFAE3F-l3A5Bk7waGM@public.gmane.org> Sender: kvm-ppc-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: kvm.vger.kernel.org On 01/10/2010 02:32 PM, Alexander Graf wrote: > > >> Applied both, and queued for .33. I was able to guess this from the description, but please mention it explicitly in the future. >> > I'm not sure what to mention. From a stability point of view, all the Book3S patches should go in .33 because they all fix severe bugs. > > But then again the question is what our goal for .33 is. If we only want to give out the message "KVM for Book3S is coming! Stay tuned!" then we shouldn't do any updates for .33. If we want to have something working to the best of our knowledge, all patches should go into .33. > Given the other 9-patch series, I'll regard .33 as a sneak preview (look but don't touch) and .34 will be the first really serious kvm ppc64 release. -- error compiling committee.c: too many arguments to function