On Wed, May 17, 2017 at 03:51:43AM -0600, Jan Beulich wrote:
> >>> On 17.05.17 at 11:34, wrote:
> > On Wed, May 17, 2017 at 03:02:26AM -0600, Jan Beulich wrote:
> >> >>> On 17.05.17 at 10:26, wrote:
> >> > On Tue, May 16, 2017 at 10:23:48AM -0600, Jan Beulich wrote:
> >> >> >>> On 16.05.17 at 17:
>>> On 17.05.17 at 11:34, wrote:
> On Wed, May 17, 2017 at 03:02:26AM -0600, Jan Beulich wrote:
>> >>> On 17.05.17 at 10:26, wrote:
>> > On Tue, May 16, 2017 at 10:23:48AM -0600, Jan Beulich wrote:
>> >> >>> On 16.05.17 at 17:55, wrote:
>> >> > On Fri, May 12, 2017 at 07:42:51AM -0600, Jan Beuli
On Wed, May 17, 2017 at 03:02:26AM -0600, Jan Beulich wrote:
> >>> On 17.05.17 at 10:26, wrote:
> > On Tue, May 16, 2017 at 10:23:48AM -0600, Jan Beulich wrote:
> >> >>> On 16.05.17 at 17:55, wrote:
> >> > On Fri, May 12, 2017 at 07:42:51AM -0600, Jan Beulich wrote:
> >> >> >>> On 19.04.17 at 17:
>>> On 17.05.17 at 10:26, wrote:
> On Tue, May 16, 2017 at 10:23:48AM -0600, Jan Beulich wrote:
>> >>> On 16.05.17 at 17:55, wrote:
>> > On Fri, May 12, 2017 at 07:42:51AM -0600, Jan Beulich wrote:
>> >> >>> On 19.04.17 at 17:11, wrote:
>> >> > Note that currently there's no support for unbindin
On Tue, May 16, 2017 at 10:23:48AM -0600, Jan Beulich wrote:
> >>> On 16.05.17 at 17:55, wrote:
> > On Fri, May 12, 2017 at 07:42:51AM -0600, Jan Beulich wrote:
> >> >>> On 19.04.17 at 17:11, wrote:
> >> > Note that currently there's no support for unbinding this interrupts.
> >>
> >> Do you pla
>>> On 16.05.17 at 17:55, wrote:
> On Fri, May 12, 2017 at 07:42:51AM -0600, Jan Beulich wrote:
>> >>> On 19.04.17 at 17:11, wrote:
>> > Note that currently there's no support for unbinding this interrupts.
>>
>> Do you plan to deal with that before this changes goes in? Aiui this
>> not working
On Fri, May 12, 2017 at 07:42:51AM -0600, Jan Beulich wrote:
> >>> On 19.04.17 at 17:11, wrote:
> > Note that currently there's no support for unbinding this interrupts.
>
> Do you plan to deal with that before this changes goes in? Aiui this
> not working means you can't pass through devices wit
>>> On 19.04.17 at 17:11, wrote:
> Note that currently there's no support for unbinding this interrupts.
Do you plan to deal with that before this changes goes in? Aiui this
not working means you can't pass through devices with pin based
interrupts once Dom0 chose to bind to them. Otoh hand you m
Achieve this by expanding pt_irq_create_bind in order to support mapping
interrupts of type PT_IRQ_TYPE_PCI to a PVH Dom0. GSIs bound to Dom0 are always
identity bound, which means the all the fields inside of the u.pci sub-struct
are ignored, and only the machine_irq is actually used in order to d
