Currently, IRQFD on arm still uses the deferred workqueue mechanism
to inject interrupts into guest, which will likely lead to a busy
context-switching from/to the kworker thread. This overhead is for
no purpose (only in my view ...) and will result in an interrupt
performance degradation.
Impleme
Hi,
On 3/17/19 3:50 PM, Raslan, KarimAllah wrote:
> On Sun, 2019-03-17 at 14:36 +, Zenghui Yu wrote:
>> Currently, IRQFD on arm still uses the deferred workqueue mechanism
>> to inject interrupts into guest, which will likely lead to a busy
>> context-switching from/to the kworker thread. This
On Sun, 17 Mar 2019 14:36:13 +,
Zenghui Yu wrote:
>
> Currently, IRQFD on arm still uses the deferred workqueue mechanism
> to inject interrupts into guest, which will likely lead to a busy
> context-switching from/to the kworker thread. This overhead is for
> no purpose (only in my view ...)
On Sun, 17 Mar 2019 19:35:48 +
Marc Zyngier wrote:
[...]
> A first approach would be to keep a small cache of the last few
> successful translations for this ITS, cache that could be looked-up by
> holding a spinlock instead. A hit in this cache could directly be
> injected. Any command that
On Sun, 2019-03-17 at 14:36 +, Zenghui Yu wrote:
> Currently, IRQFD on arm still uses the deferred workqueue mechanism
> to inject interrupts into guest, which will likely lead to a busy
> context-switching from/to the kworker thread. This overhead is for
> no purpose (only in my view ...) and
Hi all,
On 2019/3/18 3:35, Marc Zyngier wrote:
On Sun, 17 Mar 2019 14:36:13 +,
Zenghui Yu wrote:
Currently, IRQFD on arm still uses the deferred workqueue mechanism
to inject interrupts into guest, which will likely lead to a busy
context-switching from/to the kworker thread. This overhea
On Tue, 19 Mar 2019 09:09:43 +0800
Zenghui Yu wrote:
> Hi all,
>
> On 2019/3/18 3:35, Marc Zyngier wrote:
> > On Sun, 17 Mar 2019 14:36:13 +,
> > Zenghui Yu wrote:
> >>
> >> Currently, IRQFD on arm still uses the deferred workqueue mechanism
> >> to inject interrupts into guest, which wil
Hi Marc,
On 2019/3/19 18:01, Marc Zyngier wrote:
On Tue, 19 Mar 2019 09:09:43 +0800
Zenghui Yu wrote:
Hi all,
On 2019/3/18 3:35, Marc Zyngier wrote:
A first approach would be to keep a small cache of the last few
successful translations for this ITS, cache that could be looked-up by
holding
On Tue, 19 Mar 2019 15:59:00 +,
Zenghui Yu wrote:
>
> Hi Marc,
>
> On 2019/3/19 18:01, Marc Zyngier wrote:
> > On Tue, 19 Mar 2019 09:09:43 +0800
> > Zenghui Yu wrote:
> >
> >> Hi all,
> >>
> >> On 2019/3/18 3:35, Marc Zyngier wrote:
> >>> A first approach would be to keep a small cache o
On Mon, 18 Mar 2019 13:30:40 +
Marc Zyngier wrote:
Hi,
> On Sun, 17 Mar 2019 19:35:48 +
> Marc Zyngier wrote:
>
> [...]
>
> > A first approach would be to keep a small cache of the last few
> > successful translations for this ITS, cache that could be looked-up by
> > holding a spinlo
Hi Andre,
On Wed, 15 May 2019 17:38:32 +0100,
Andre Przywara wrote:
>
> On Mon, 18 Mar 2019 13:30:40 +
> Marc Zyngier wrote:
>
> Hi,
>
> > On Sun, 17 Mar 2019 19:35:48 +
> > Marc Zyngier wrote:
> >
> > [...]
> >
> > > A first approach would be to keep a small cache of the last few
Hi Marc,
On 2019/5/16 15:21, Marc Zyngier wrote:
Hi Andre,
On Wed, 15 May 2019 17:38:32 +0100,
Andre Przywara wrote:
On Mon, 18 Mar 2019 13:30:40 +
Marc Zyngier wrote:
Hi,
On Sun, 17 Mar 2019 19:35:48 +
Marc Zyngier wrote:
[...]
A first approach would be to keep a small cache
On Mon, 2019-05-20 at 23:31 +0800, Zenghui Yu wrote:
> Hi Marc,
>
> On 2019/5/16 15:21, Marc Zyngier wrote:
> >
> > Hi Andre,
> >
> > On Wed, 15 May 2019 17:38:32 +0100,
> > Andre Przywara wrote:
> > >
> > >
> > > On Mon, 18 Mar 2019 13:30:40 +
> > > Marc Zyngier wrote:
> > >
> > > Hi,
13 matches
Mail list logo
