Dear John,
I would speak about XEN on ARM further.
Basically you need a passthrough in XEN terms in case you want a bus
initiator (i.e. DMA capable) device to be assigned to DomU.
For a passive device it's pretty enough to assign MMIO ranges and
interrupts using guest domain config. The pit
Hello,
On 23/05/17 14:18, Jan Beulich wrote:
On 23.05.17 at 14:53, wrote:
Thanks for the reply. we are using renesas rcar h3 board. Does it supports?
A general rule is to provide as much as details on your mail so we can
provide the best feedback.
In this case, I don't fully understand wh
>>> On 23.05.17 at 14:53, wrote:
> Thanks for the reply. we are using renesas rcar h3 board. Does it supports?
I have no idea, I'm an x86 person.
Also please don't top-post.
Jan
> On Tuesday, May 23, 2017, Jan Beulich wrote:
>
>> >>> On 23.05.17 at 11:38, >
>> wrote:
>> > Is it possible to g
Thanks for the reply. we are using renesas rcar h3 board. Does it supports?
On Tuesday, May 23, 2017, Jan Beulich wrote:
> >>> On 23.05.17 at 11:38, >
> wrote:
> > Is it possible to give each channels of uart to different guests via pass
> > through mechanism?
>
> If each channel is represented
>>> On 23.05.17 at 11:38, wrote:
> Is it possible to give each channels of uart to different guests via pass
> through mechanism?
If each channel is represented by a separate PCI device/function,
then likely yes. If they're all one PCI device, or not a PCI device
at all, then you may be able to h
Hi,
Is it possible to give each channels of uart to different guests via pass
through mechanism?
regards
Georgeeldhojohn
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
On Fri, 2015-10-23 at 13:38 +0100, David Vrabel wrote:
> On 23/10/15 13:37, Ian Campbell wrote:
> > On Fri, 2015-10-23 at 12:05 +0100, David Vrabel wrote:
> > > When injecting an interrupt for a passthrough device into a guest,
> > > the
> > > per-domain event_lock is held, reducing performance whe
On Fri, 2015-10-23 at 12:05 +0100, David Vrabel wrote:
> When injecting an interrupt for a passthrough device into a guest, the
> per-domain event_lock is held, reducing performance when a guest has
> many VCPUs and high interrupt rates.
Did you CC me due to a possible impact on ARM? If so then I
On 23/10/15 13:37, Ian Campbell wrote:
> On Fri, 2015-10-23 at 12:05 +0100, David Vrabel wrote:
>> When injecting an interrupt for a passthrough device into a guest, the
>> per-domain event_lock is held, reducing performance when a guest has
>> many VCPUs and high interrupt rates.
>
> Did you CC m
When injecting an interrupt for a passthrough device into a guest, the
per-domain event_lock is held, reducing performance when a guest has
many VCPUs and high interrupt rates.
By using a per-interrupt lock in the hot paths, this contention is
eliminated and performance improves (a bit).
For test
10 matches
Mail list logo
