Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-16 Thread Jan Beulich
On 02.10.2023 17:11, Roger Pau Monne wrote: > Since it was indicated that introducing specific new vCPU ops may be > beneficial independent of the introduction of a fully physical- > address-based ABI flavor, here we go. There continue to be a few open > questions throughout the series, resolving o

Re: [CRITICAL for 4.18] Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-16 Thread Jan Beulich
On 05.10.2023 20:58, Andrew Cooper wrote: > I see this series has been committed.  But it's broken in a really > fundamental way. > > > This is a new extension with persistent side effects to an existing part > of the guest ABI. > > Yet there doesn't appear to be any enumeration that the interfa

Re: [CRITICAL for 4.18] Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-06 Thread Andrew Cooper
On 06/10/2023 9:00 am, Roger Pau Monné wrote: > On Thu, Oct 05, 2023 at 07:58:50PM +0100, Andrew Cooper wrote: >> Henry: Blocker for 4.18.   The absolutely bare minimum necessary to >> avoid reversion is some kind of positive enumeration that the two new >> hypercalls are available. >> >> Otherwise

Re: [CRITICAL for 4.18] Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-06 Thread Roger Pau Monné
On Fri, Oct 06, 2023 at 10:00:35AM +0200, Roger Pau Monné wrote: > On Thu, Oct 05, 2023 at 07:58:50PM +0100, Andrew Cooper wrote: > > I see this series has been committed.  But it's broken in a really > > fundamental way. > > > > > > This is a new extension with persistent side effects to an exis

Re: [CRITICAL for 4.18] Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-06 Thread Roger Pau Monné
On Thu, Oct 05, 2023 at 07:58:50PM +0100, Andrew Cooper wrote: > I see this series has been committed.  But it's broken in a really > fundamental way. > > > This is a new extension with persistent side effects to an existing part > of the guest ABI. The only change in the ABI is the different re

Re: [CRITICAL for 4.18] Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-05 Thread Julien Grall
On 05/10/2023 23:40, Julien Grall wrote: Hi Andrew, On 05/10/2023 19:58, Andrew Cooper wrote: I see this series has been committed.  But it's broken in a really fundamental way. Thanks for pointing out. But I'd like to understand how I come to only hear about those concerns on the series

Re: [CRITICAL for 4.18] Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-05 Thread Julien Grall
Hi Andrew, On 05/10/2023 19:58, Andrew Cooper wrote: I see this series has been committed.  But it's broken in a really fundamental way. Thanks for pointing out. But I'd like to understand how I come to only hear about those concerns on the series after committing. Did I miss any thread? Eve

[CRITICAL for 4.18] Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-05 Thread Andrew Cooper
I see this series has been committed.  But it's broken in a really fundamental way. This is a new extension with persistent side effects to an existing part of the guest ABI. Yet there doesn't appear to be any enumeration that the interface is available to begin with.  Requiring the guest to pro

Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-05 Thread Julien Grall
Hi, On 05/10/2023 02:27, Henry Wang wrote: Hi Roger, On Oct 2, 2023, at 23:11, Roger Pau Monne wrote: Since it was indicated that introducing specific new vCPU ops may be beneficial independent of the introduction of a fully physical- address-based ABI flavor, here we go. There continue to b

Re: [PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-04 Thread Henry Wang
Hi Roger, > On Oct 2, 2023, at 23:11, Roger Pau Monne wrote: > > Since it was indicated that introducing specific new vCPU ops may be > beneficial independent of the introduction of a fully physical- > address-based ABI flavor, here we go. There continue to be a few open > questions throughout t

[PATCH v5 00/10] runstate/time area registration by (guest) physical address

2023-10-02 Thread Roger Pau Monne
Since it was indicated that introducing specific new vCPU ops may be beneficial independent of the introduction of a fully physical- address-based ABI flavor, here we go. There continue to be a few open questions throughout the series, resolving of which was one of the main goals of the earlier pos