All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel@lists.xenproject.org,
	Stefano Stabellini <sstabellini@kernel.org>,
	Andrii Anisov <andrii_anisov@epam.com>,
	Andrii Anisov <andrii.anisov@gmail.com>
Subject: Re: [PATCH v2] gic: drop interrupts enabling on interrupts processing
Date: Fri, 31 May 2019 18:28:44 +0100	[thread overview]
Message-ID: <20190531182844.0cd43909@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <959c8e20-705e-b654-d87c-916c2bdf29f4@arm.com>

On Fri, 31 May 2019 18:16:52 +0100
Julien Grall <julien.grall@arm.com> wrote:

> Hi,
> 
> On 30/05/2019 17:14, Andrii Anisov wrote:
> > 
> > 
> > On 29.05.19 18:32, Julien Grall wrote:  
> >>> BTW, do you hear about plans for the new vgic? Some time ago it was said that 
> >>> new vgic implementation going to replace the old one, and optimizing the old 
> >>> is worthless. But as I see, there are no updates into that area yet.  
> >>
> >> We need help to make it happen.  
> > I'm not sure I'll have spare time soon, but what kind of help you need? Do you 
> > have a TODO list?  
> 
>  From the top of my head the major blocker is GICv3 (+ ITS) support. It mostly 
> need to be ported from Linux.
> 
> There were also a couple of concern regarding using ordering the list while 
> folding (can't remember if this was addressed in Linux).
> 
> @Andre, I thought we capture that in Xen Project jira but I can't find it. Did 
> you keep a list?

I thought Jira as well, but apparently we never actually did this :-(

So yes, GICv3 support is the showstopper here, this would allow us to make the new VGIC the default, since we would have feature parity.

Also we would need to check the git log in Linux for the individual VGIC files to port over fixes, if applicable. Due to the different coding style and renamed identifiers, comparing the files does not really help.

Cheers,
Andre.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Andre Przywara <andre.przywara@arm.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel@lists.xenproject.org,
	Stefano Stabellini <sstabellini@kernel.org>,
	Andrii Anisov <andrii_anisov@epam.com>,
	Andrii Anisov <andrii.anisov@gmail.com>
Subject: Re: [Xen-devel] [PATCH v2] gic: drop interrupts enabling on interrupts processing
Date: Fri, 31 May 2019 18:28:44 +0100	[thread overview]
Message-ID: <20190531182844.0cd43909@donnerap.cambridge.arm.com> (raw)
Message-ID: <20190531172844.RP7V25GAY-0H8ZAdVy_dvgvDzGX3r5myUa2kpwFhsME@z> (raw)
In-Reply-To: <959c8e20-705e-b654-d87c-916c2bdf29f4@arm.com>

On Fri, 31 May 2019 18:16:52 +0100
Julien Grall <julien.grall@arm.com> wrote:

> Hi,
> 
> On 30/05/2019 17:14, Andrii Anisov wrote:
> > 
> > 
> > On 29.05.19 18:32, Julien Grall wrote:  
> >>> BTW, do you hear about plans for the new vgic? Some time ago it was said that 
> >>> new vgic implementation going to replace the old one, and optimizing the old 
> >>> is worthless. But as I see, there are no updates into that area yet.  
> >>
> >> We need help to make it happen.  
> > I'm not sure I'll have spare time soon, but what kind of help you need? Do you 
> > have a TODO list?  
> 
>  From the top of my head the major blocker is GICv3 (+ ITS) support. It mostly 
> need to be ported from Linux.
> 
> There were also a couple of concern regarding using ordering the list while 
> folding (can't remember if this was addressed in Linux).
> 
> @Andre, I thought we capture that in Xen Project jira but I can't find it. Did 
> you keep a list?

I thought Jira as well, but apparently we never actually did this :-(

So yes, GICv3 support is the showstopper here, this would allow us to make the new VGIC the default, since we would have feature parity.

Also we would need to check the git log in Linux for the individual VGIC files to port over fixes, if applicable. Due to the different coding style and renamed identifiers, comparing the files does not really help.

Cheers,
Andre.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-05-31 17:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27  9:29 [PATCH v2] gic: drop interrupts enabling on interrupts processing Andrii Anisov
2019-05-27  9:29 ` [Xen-devel] " Andrii Anisov
2019-05-28 17:07 ` Julien Grall
2019-05-28 17:07   ` [Xen-devel] " Julien Grall
2019-05-29 10:31   ` Andrii Anisov
2019-05-29 10:31     ` [Xen-devel] " Andrii Anisov
2019-05-29 15:32     ` Julien Grall
2019-05-29 15:32       ` [Xen-devel] " Julien Grall
2019-05-30 16:12       ` Andrii Anisov
2019-05-30 16:12         ` [Xen-devel] " Andrii Anisov
2019-05-31 17:11         ` Julien Grall
2019-05-31 17:11           ` [Xen-devel] " Julien Grall
2019-05-31 20:08           ` Stefano Stabellini
2019-05-31 20:08             ` [Xen-devel] " Stefano Stabellini
2019-06-10 15:49           ` Andrii Anisov
2019-06-10 19:51             ` Julien Grall
2019-06-11  7:38               ` Andrii Anisov
2019-05-30 16:14       ` Andrii Anisov
2019-05-30 16:14         ` [Xen-devel] " Andrii Anisov
2019-05-31 17:16         ` Julien Grall
2019-05-31 17:16           ` [Xen-devel] " Julien Grall
2019-05-31 17:28           ` Andre Przywara [this message]
2019-05-31 17:28             ` Andre Przywara
2019-05-31 17:25   ` Andre Przywara
2019-05-31 17:25     ` [Xen-devel] " Andre Przywara
2019-05-31 17:54     ` Julien Grall
2019-05-31 17:54       ` [Xen-devel] " Julien Grall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190531182844.0cd43909@donnerap.cambridge.arm.com \
    --to=andre.przywara@arm.com \
    --cc=andrii.anisov@gmail.com \
    --cc=andrii_anisov@epam.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.