Re: [PATCH v2 0/4] Manage vcpu flags from the host

2020-07-22 Thread Dave Martin
On Wed, Jul 22, 2020 at 05:36:34PM +0100, Marc Zyngier wrote: > On 2020-07-22 17:24, Dave Martin wrote: > >On Mon, Jul 13, 2020 at 10:05:01PM +0100, Andrew Scull wrote: > >>The aim is to keep management of the flags in the host and out of hyp > >>where possible. I find this makes it easier to under

Re: [PATCH v2 0/4] Manage vcpu flags from the host

2020-07-22 Thread Marc Zyngier
On 2020-07-22 17:24, Dave Martin wrote: On Mon, Jul 13, 2020 at 10:05:01PM +0100, Andrew Scull wrote: The aim is to keep management of the flags in the host and out of hyp where possible. I find this makes it easier to understand how the flags are used as the responsibilities are clearly divid

Re: [PATCH v2 0/4] Manage vcpu flags from the host

2020-07-22 Thread Dave Martin
On Mon, Jul 13, 2020 at 10:05:01PM +0100, Andrew Scull wrote: > The aim is to keep management of the flags in the host and out of hyp > where possible. I find this makes it easier to understand how the flags > are used as the responsibilities are clearly divided. > > The series applies on top of k

[PATCH v2 0/4] Manage vcpu flags from the host

2020-07-13 Thread Andrew Scull
The aim is to keep management of the flags in the host and out of hyp where possible. I find this makes it easier to understand how the flags are used as the responsibilities are clearly divided. The series applies on top of kvmarm/next after VHE and nVHE have been separated. >From v1 <2020071009