Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

2017-04-04 Thread Sander Eikelenboom
On 04/04/17 18:07, Konrad Rzeszutek Wilk wrote: > On Mon, Apr 03, 2017 at 02:22:36PM +0200, Sander Eikelenboom wrote: >> On 31/03/17 16:38, Konrad Rzeszutek Wilk wrote: >>> On Fri, Mar 31, 2017 at 04:46:27AM -0600, Jan Beulich wrote: >>> On 31.03.17 at 10:07, wrote: > On Fri, Mar 31, 2017

Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

2017-04-04 Thread Konrad Rzeszutek Wilk
On Mon, Apr 03, 2017 at 02:22:36PM +0200, Sander Eikelenboom wrote: > On 31/03/17 16:38, Konrad Rzeszutek Wilk wrote: > > On Fri, Mar 31, 2017 at 04:46:27AM -0600, Jan Beulich wrote: > > On 31.03.17 at 10:07, wrote: > >>> On Fri, Mar 31, 2017 at 05:05:44AM +, Tian, Kevin wrote: > > Fro

Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

2017-04-03 Thread Sander Eikelenboom
On 31/03/17 16:38, Konrad Rzeszutek Wilk wrote: > On Fri, Mar 31, 2017 at 04:46:27AM -0600, Jan Beulich wrote: > On 31.03.17 at 10:07, wrote: >>> On Fri, Mar 31, 2017 at 05:05:44AM +, Tian, Kevin wrote: > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Monday, March 27, 2017 4

Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

2017-03-31 Thread Konrad Rzeszutek Wilk
On Fri, Mar 31, 2017 at 04:46:27AM -0600, Jan Beulich wrote: > >>> On 31.03.17 at 10:07, wrote: > > On Fri, Mar 31, 2017 at 05:05:44AM +, Tian, Kevin wrote: > >> > From: Jan Beulich [mailto:jbeul...@suse.com] > >> > Sent: Monday, March 27, 2017 4:00 PM > >> > > >> > >>> On 24.03.17 at 17:54,

Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

2017-03-31 Thread Jan Beulich
>>> On 31.03.17 at 10:07, wrote: > On Fri, Mar 31, 2017 at 05:05:44AM +, Tian, Kevin wrote: >> > From: Jan Beulich [mailto:jbeul...@suse.com] >> > Sent: Monday, March 27, 2017 4:00 PM >> > >> > >>> On 24.03.17 at 17:54, wrote: >> > > As I understand it, for level triggered legacy PCI interru

Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

2017-03-31 Thread Roger Pau Monné
On Fri, Mar 31, 2017 at 05:05:44AM +, Tian, Kevin wrote: > > From: Jan Beulich [mailto:jbeul...@suse.com] > > Sent: Monday, March 27, 2017 4:00 PM > > > > >>> On 24.03.17 at 17:54, wrote: > > > As I understand it, for level triggered legacy PCI interrupts Xen sets > > > up a timer in order to

Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

2017-03-30 Thread Tian, Kevin
> From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Monday, March 27, 2017 4:00 PM > > >>> On 24.03.17 at 17:54, wrote: > > As I understand it, for level triggered legacy PCI interrupts Xen sets > > up a timer in order to perform the EOI if the guest takes too long in > > deasserting the line.

Re: [Xen-devel] Legacy PCI interrupt {de}assertion count

2017-03-27 Thread Jan Beulich
>>> On 24.03.17 at 17:54, wrote: > As I understand it, for level triggered legacy PCI interrupts Xen sets up a > timer in order to perform the EOI if the guest takes too long in deasserting > the line. This is done in pt_irq_time_out. What I don't understand is why this > function also does a deas

[Xen-devel] Legacy PCI interrupt {de}assertion count

2017-03-24 Thread Roger Pau Monné
Hello, I have a question related to how Xen accounts the legacy PCI interrupt assertions when binding interrupts to HVM guests. It's probably just me not properly understand this code (or missing bits of it). As I understand it, for level triggered legacy PCI interrupts Xen sets up a timer in ord