[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <577D3854.6090407@de.ibm.com>
Date: Wed, 6 Jul 2016 18:56:52 +0200
From: Christian Borntraeger <borntraeger@...ibm.com>
To: Peter Zijlstra <peterz@...radead.org>,
Juergen Gross <jgross@...e.com>
Cc: Pan Xinhui <xinhui.pan@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
virtualization@...ts.linux-foundation.org,
linux-s390@...r.kernel.org, mingo@...hat.com, mpe@...erman.id.au,
paulus@...ba.org, benh@...nel.crashing.org,
paulmck@...ux.vnet.ibm.com, waiman.long@....com,
will.deacon@....com, boqun.feng@...il.com, dave@...olabs.net,
schwidefsky@...ibm.com, pbonzini@...hat.com,
xen-devel-request@...ts.xenproject.org,
Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: [PATCH v2 0/4] implement vcpu preempted check
On 07/06/2016 10:19 AM, Peter Zijlstra wrote:
> On Wed, Jul 06, 2016 at 09:47:18AM +0200, Juergen Gross wrote:
>> On 06/07/16 08:52, Peter Zijlstra wrote:
>
>>> Paolo, could you help out with an (x86) KVM interface for this?
>>
>> Xen support of this interface should be rather easy. Could you please
>> Cc: xen-devel-request@...ts.xenproject.org in the next version?
>
> So meta question; aren't all you virt people looking at the regular
> virtualization list? Or should we really dig out all the various
> hypervisor lists and Cc them?
>
Some of the kvm on s390 team reads this, but I would assume that the base s390 team
does not (Martin can you confirm?) as the main focus was z/VM and LPAR. So maybe adding
linux-s390@...r for generic things does make sense.
Powered by blists - more mailing lists