mitt...@xenproject.org; xen-
> de...@lists.xenproject.org; Juergen Gross
> Subject: Re: [PATCH v6 0/3] XSA-343 followup patches
>
> Hi Jan,
>
> On 18/11/2020 08:22, Jan Beulich wrote:
> > On 17.11.2020 19:13, Julien Grall wrote:
> >> On 09/11/2020 16:38, Juergen
Julien Grall writes ("Re: [PATCH v6 0/3] XSA-343 followup patches"):
> On 18/11/2020 08:22, Jan Beulich wrote:
> > Without a clear outline of what would break with the present logic,
> > I had previously indicated I'm not convinced of the change. This
> > isn&#
Hi Jan,
On 18/11/2020 08:22, Jan Beulich wrote:
On 17.11.2020 19:13, Julien Grall wrote:
On 09/11/2020 16:38, Juergen Gross wrote:
Juergen Gross (3):
xen/events: access last_priority and last_vcpu_id together
xen/evtchn: rework per event channel lock
xen/evtchn: revert 52e1fc47abc3
On 18.11.2020 09:41, Jürgen Groß wrote:
> On 18.11.20 09:22, Jan Beulich wrote:
>> On 17.11.2020 19:13, Julien Grall wrote:
>>> On 09/11/2020 16:38, Juergen Gross wrote:
Juergen Gross (3):
xen/events: access last_priority and last_vcpu_id together
xen/evtchn: rework per event
On 18.11.20 09:22, Jan Beulich wrote:
On 17.11.2020 19:13, Julien Grall wrote:
On 09/11/2020 16:38, Juergen Gross wrote:
Juergen Gross (3):
xen/events: access last_priority and last_vcpu_id together
xen/evtchn: rework per event channel lock
xen/evtchn: revert 52e1fc47abc3a0123
Whi
On 17.11.2020 19:13, Julien Grall wrote:
> On 09/11/2020 16:38, Juergen Gross wrote:
>> Juergen Gross (3):
>>xen/events: access last_priority and last_vcpu_id together
>>xen/evtchn: rework per event channel lock
>>xen/evtchn: revert 52e1fc47abc3a0123
>
> While looking at the list of co
Hi,
On 09/11/2020 16:38, Juergen Gross wrote:
The patches for XSA-343 produced some fallout, especially the event
channel locking has shown to be problematic.
Patch 1 is targeting fifo event channels for avoiding any races for the
case that the fifo queue has been changed for a specific event c
