>>> Ian Jackson 09/17/15 8:02 PM >>>
>Tim Deegan writes ("Re: [PATCH v2] MAINTAINERS: Document maintainers for
>xen/common/"):
>> I would rather your v1 plus an appropriate change to get_maintainers.
>
>I am happy to implement in get_maintainers whatever is decided.
>
>>> George Dunlap 09/17/15 4:30 PM >>>
>On 09/17/2015 01:40 PM, Dario Faggioli wrote:
>So one option is to do the "blocking" stuff in an arch-specific call
>from vcpu_block():
>
>vcpu_block()
>set(_VPF_blocked)
>v->arch.block()
>- Add v to pcpu.pi_blocked_vcpu
>-
On Fri, Sep 18, 2015 at 05:34:24PM +0200, Paolo Bonzini wrote:
> These have roughly the same purpose as the SMRR, which we do not need
> to implement in KVM. However, Linux accesses MSR_K8_TSEG_ADDR at
> boot, which causes problems when running a Xen dom0 under KVM.
> Just return 0, meaning that
flight 62082 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62082/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 5 kernel-build fail REGR. vs. 60684
flight 62073 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62073/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 2f667c5488c81924861901d4d7c6f4bb170ffb69
baseline version:
ovmf
This run is configured for baseline tests only.
flight 37967 qemu-upstream-4.3-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37967/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-ovmf-amd64 9
On Fri, Sep 18, 2015 at 08:20:46AM -0700, Andy Lutomirski wrote:
> In any event, Borislav, you must have typed rdmsr_safe for a reason :)
Wasn't me:
6c62aa4a3c12 ("x86: make amd.c have 64bit support code")
I think the error handling of rdmsrl_safe() was needed to do the pfn
games which are done
flight 62066 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62066/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-vhd 6 xen-boot fail REGR. vs. 61911
flight 62047 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62047/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-raw9 debian-di-install fail REGR. vs. 60727
Hi Julien,
static int vgic_v3_distr_mmio_read(struct vcpu *v, mmio_info_t *info)
{
...
case GICD_TYPER:
{
/*
* Number of interrupt identifier bits supported by the GIC
* Stream Protocol Interface
*/
On Thu, 2015-09-17 at 19:36 +0100, Anthony PERARD wrote:
> The commit have been reverted, so everything should be back to normal.
Great, thanks.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On Thu, 2015-09-17 at 18:45 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST] README.dev: Some words on what is
> needed when updating the daemons."):
> > +- ms-ownerdaemon
> > +
> > +Requires restarting. This cannot be done while any jobs are in
> > +progress. Don't forget
On Thu, 2015-09-17 at 18:42 +0100, Julien Grall wrote:
> On 17/09/15 18:36, Julien Grall wrote:
> > When creating a guest with more than 3GB of memory, the 2 banks will be
> > used and the loop with overrunning. The code will fail later on because
> > Xen will deny to populate the region:
> >
> >
On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
> Give this a GPLv2+ licence so that we can move it into some other
> FLOSS package later.
>
> Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
> SQL has no portable boolean true literal (really). SQLite3 does not
> understand `TRUE'. Use `1=1' instead.
>
> This means that mg-show-flight-runvars -a will work in standalone
> mode.
>
> Signed-off-by: Ian Jackson
On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
> Make mg-show-flight-runvars -a append ~ to the names of synth runvars.
> (This is consistent with the new syntax in cs-job-create.)
>
> We do this by editing $row[1] (and $colws[1]) so we can avoid
> disturbing the general column format
On Thu, 2015-09-17 at 18:58 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH v2 for-4.6] libxl: handle read-only
> drives with qemu-xen"):
> > So shall we go ahead with this for 4.6 or is there more
> > testing/discussion/whatever needed?
>
> I think we can commit it to 4.6. I would
Hi everyone,
Thanks for your prompt reply.
@Lars- I think I would like to work in a Mirage OS related project as of
now. Because I'm fairly new to it, request you to give me a few small bugs
to solve.
Sincerely,
Lasya V
On 18 September 2015 at 01:44, Konrad Rzeszutek Wilk
flight 62049 linux-3.16 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62049/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops 4 host-build-prep fail in 61939 REGR. vs. 60836
Tests which are
On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
> The smoke tests are for testing xen-unstable. We want to avoid
> building anything else. So arrange to reuse previous builds by
> calling mg-adjust-flight-makexrefs.
>
> Signed-off-by: Ian Jackson
> ---
> v2:
On 18/09/15 10:48, Vijay Kilari wrote:
> On Fri, Sep 18, 2015 at 2:03 PM, Ian Campbell wrote:
>> On Fri, 2015-09-18 at 12:56 +0530, Vijay Kilari wrote:
>>> Hi Julien,
>>>
>>> static int vgic_v3_distr_mmio_read(struct vcpu *v, mmio_info_t *info)
>>> {
>>> ...
>>>
Dom0: Squeeze 64 bit with kernel 4.1.6 and xen stable-4.6 based on
commit 70d63e48077f8fee8eda6d8d95eeda52a34d9077
DomU W7 pro 64 bit with new pv drivers, xl cfg in attachment.
Qemu crash on windows boot with this line in log:
Bad ram offset 805b1000
xl dmesg about the domU:
(d4) HVM Loader
On Fri, 2015-09-18 at 12:56 +0530, Vijay Kilari wrote:
> Hi Julien,
>
> static int vgic_v3_distr_mmio_read(struct vcpu *v, mmio_info_t *info)
> {
> ...
>case GICD_TYPER:
>{
>/*
> * Number of interrupt identifier bits supported by the
On Thu, 2015-09-17 at 13:53 +0200, Mike Belopuhov wrote:
A few words here about the methodology you used to determine the names to
use would be useful to people looking back on this stuff in the future.
Also it would be sensible to CC everyone whose name you are adding. I've
added Keir since you
On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
> This provides a fairly cooked way of adjusting an existing flight to
> reuse previous builds.
>
> Signed-off-by: Ian Jackson
How exciting.
Acked-by: Ian Campbell
> ---
> v2: New patch
* Andy Lutomirski wrote:
> This demotes an OOPS and likely panic due to a failed non-"safe" MSR
> access to a WARN_ON_ONCE and a return of poisoned values (in the
> RDMSR case). We still write a pr_info entry unconditionally for
> debugging.
>
> To be clear, this type of
On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
> Specifies that returned information should relate to a flight in which
> a particular job existed and passed. The option can be repeated if
> desired (to specify flights in which _all_ those jobs passed).
>
> Signed-off-by: Ian Jackson
On Fri, Sep 18, 2015 at 2:03 PM, Ian Campbell wrote:
> On Fri, 2015-09-18 at 12:56 +0530, Vijay Kilari wrote:
>> Hi Julien,
>>
>> static int vgic_v3_distr_mmio_read(struct vcpu *v, mmio_info_t *info)
>> {
>> ...
>>case GICD_TYPER:
>>{
>>
Although we already have 'gfx_passthru' in b_info, this doesn't suffice
after we want to handle IGD specifically. Now we define a new field of
type, gfx_passthru_kind, to indicate we're trying to pass IGD. Actually
this means we can benefit this to support other specific devices just
by extending
On Fri, 2015-09-18 at 00:27 -0600, Jan Beulich wrote:
> > George Dunlap 09/17/15 4:30 PM >>>The
> > > > vcpu_block()
> >set(_VPF_blocked)
> >v->arch.block()
> >- Add v to pcpu.pi_blocked_vcpu
> >- NV => pi_wakeup_vector
> >local_events_need_delivery()
>
At 19:02 +0100 on 17 Sep (1442516564), Ian Jackson wrote:
> Tim Deegan writes ("Re: [PATCH v2] MAINTAINERS: Document maintainers for
> xen/common/"):
> > I would rather your v1 plus an appropriate change to get_maintainers.
>
> I am happy to implement in get_maintainers whatever is decided.
>
>
Add this branch to select_xenbranch. This works like xen-unstable in
most respects.
There are only two places in osstest where xenbranch `xen-unstable' is
treated specially and only one of them needs adjusting to match
xen-unstable-smoke too.
The new branch `xen-unstable-smoke' has a `prev'
This function is now called for almost every timeout.
Specifically, it is called in the cases in TestSupport where a guest-
or host-related timeout is passed from code which has a $ho or $gho,
to code which does not: all callers of poll_loop, and tcmd.
Currently the function is a no-op. Its
debian-7.2.0-i386-CD-1.iso contains no grub, only isolinux.
If the specified EFI grub file does not exist, fall back to isolinux.
This requires a -c option as well, according to
https://wiki.debian.org/DebianInstaller/Modify/CD
Only try to set up a grub config if we are booting grub. (The
$gsuite was set from guest_var, but before $gho was set, leading to an
undefined value warning from Perl.
This would ignore any guest-specific suite runvars. AFAICT these are
set by some of the jobs in make-distros-flight. I think the effect of
this change is to apply workarounds for the
Empirically, the device shows up as /dev/sda.
Signed-off-by: Ian Jackson
---
make-flight |6 --
ts-debian-hvm-install |4 +++-
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/make-flight b/make-flight
index accf922..2552a53 100755
On 09/18/2015 03:04 PM, Borislav Petkov wrote:
> On Fri, Sep 18, 2015 at 08:20:46AM -0700, Andy Lutomirski wrote:
>> Given that we can handle fixups in the decompressor, surely it
>> wouldn't be so hard to make early GPF fixups work in the main kernel.
>
> Frankly, I still am wondering what a
Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
---
crontab |1 +
1 file changed, 1 insertion(+)
diff --git a/crontab b/crontab
index 436645b..b9d4ad1 100644
--- a/crontab
+++ b/crontab
@@ -2,6 +2,7 @@
If we are booting our install ISO using a non-EFI executable, don't
try to provide an EFI for the installed system either.
Signed-off-by: Ian Jackson
---
ts-debian-hvm-install |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
On Wed, Sep 16, 2015 at 12:12 PM, Razvan Cojocaru wrote:
> On 09/16/2015 06:57 PM, Tamas K Lengyel wrote:
> >
> >
> > On Tue, Sep 15, 2015 at 5:19 AM, Razvan Cojocaru
> > > wrote:
> >
> > A previous
On 9/3/15 10:00 AM, Jan Beulich wrote:
On 03.09.15 at 16:04, wrote:
>> On 9/3/15 5:31 AM, Jan Beulich wrote:
>> On 02.09.15 at 19:50, wrote:
* target only the xen/ directory tree (i.e. not the toolstack, stubdoms
or docs)
>>>
>>> As just
Thanks for the reviews.
My play cr-daily-branch run revealed that:
1. The cr-* branch plumbing was wrong. So I have redone that
patch and dropped your ack.
2. test-amd64-amd64-xl-qemuu-debianhvm-i386 was broken due to
problems mostly with ts-debian-hvm-install. This results in
9
The branches and push gates are now:
xen.git#staging -[xen-unstable-smoke]-> #smoke -[xen-unstable]-> #master
Deployment note: When this passes the osstest self-push-gate, the main
xen-unstable flight will start using smoke as an input. Therefore,
until the new cronjob is installed to run the
ts-debian-hvm-install hardcoded `install.amd' as the directory in the
.iso in which to find the kernel and initrd. This is wrong for
architectures other than amd64.
Instead, pass this information in runvars (as is done for the netinst
installs in make-distros-flight), and honour it in
This is not technically needed as bash interprets `a=1 b=2' as
settings of both a and b. But it's not idiomatic sh within osstest to
use this syntax.
No functional change.
Signed-off-by: Ian Jackson
---
cri-common |2 +-
1 file changed, 1 insertion(+), 1
We look up a guest runvar GUEST_CONTEXT_timeoutfactor (according to
the usual rules for guest runvars).
Here CONTEXT can currently be `general' or `install'. (`install'
applies when the guest is being installed.) If the runvar exists, all
timeouts relating to that guest in that context are
The Debian i386 image boots a 32-bit non-PAE kernel which therefore
cannot have any PV drivers on our 64-bit hypervisors. This makes it a
bit slow: in my test on a machine under my desk it took 1400s out of
the allowed 2000s.
With this change the timeout is 3000s instead.
Signed-off-by: Ian
This variable appears to be unused throughout the code base.
Signed-off-by: Doug Goldstein
---
Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index 75177f0..8a9331f 100644
--- a/Makefile
+++ b/Makefile
@@ -35,8 +35,7 @@
flight 62060 linux-3.10 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62060/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qcow2 9 debian-di-install fail REGR. vs. 60670
flight 62075 qemu-upstream-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62075/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-vhd9 debian-di-install fail REGR. vs. 60577
This run is configured for baseline tests only.
flight 37968 qemu-upstream-4.4-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37968/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
flight 62080 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62080/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-vhd 6 xen-boot fail REGR. vs. 61627
And here we are, finally... :-/
On Sun, 2015-07-12 at 22:13 -1000, Justin T. Weaver wrote:
> by making sure that vcpus only run on the pcpu(s) they are allowed to
> run on based on their hard affinity cpu masks.
>
> Signed-off-by: Justin T. Weaver
>
So, this patch looks now
flight 62062 qemu-upstream-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62062/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-vhd9 debian-di-install fail REGR. vs. 60565
This run is configured for baseline tests only.
flight 37965 qemu-upstream-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37965/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl-vhd 9 debian-di-install
On Fri, 2015-09-18 at 10:02 +0100, Ian Campbell wrote:
> On Wed, 2015-09-16 at 14:07 +0100, Ian Campbell wrote:
> > [...]
> > +sub add_event($) {
> > +my ($job,$reso,$type,$info,$time) = @_;
> > +
> > +die unless $type =~ m/^(Start|End)/;
> > +
> > +$job->{OverallTime} //= {};
> >
Ian Campbell writes ("Re: [OSSTEST PATCH 29/33] make-flight: Provide
xen-unstable-smoke branch"):
> On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
...
> > We override host allocator parameters to make this flight not care
> > about host stickiness: it just takes whatever comes to hand.
On Fri, 2015-09-18 at 12:18 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH 29/33] make-flight: Provide xen
> -unstable-smoke branch"):
> > On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
> ...
> > > We override host allocator parameters to make this flight not care
> >
On 18/09/15 12:40, Zhang, Yang Z wrote:
> Jan Beulich wrote on 2015-09-18:
> "Zhang, Yang Z" 09/18/15 2:29 AM >>>
>>> Zhang, Yang Z wrote on 2015-09-08:
>>> I have a quick check on current code. I am curious that is current Xen
>>> preemptive?
>>>
>>> Also, when return
flight 62053 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62053/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-credit2 16 guest-start/debian.repeat fail in 61947 pass in
62053
On Fri, Sep 18, 2015 at 09:52:44AM +0100, Ian Campbell wrote:
> On Thu, 2015-09-17 at 18:42 +0100, Julien Grall wrote:
> > On 17/09/15 18:36, Julien Grall wrote:
> > > When creating a guest with more than 3GB of memory, the 2 banks will be
> > > used and the loop with overrunning. The code will
Jan Beulich wrote on 2015-09-18:
"Zhang, Yang Z" 09/18/15 2:29 AM >>>
>> Zhang, Yang Z wrote on 2015-09-08:
>> I have a quick check on current code. I am curious that is current Xen
>> preemptive?
>>
>> Also, when return from an interrupt handler, hypervisor didn't
On 17/09/15 19:45, Konrad Rzeszutek Wilk wrote:
> . snip..
>> The build id of the current running hypervisor should belong in the
>> xeninfo hypercall. It is not specific to xsplice.
> However in the previous reviews it was pointed out that it should only be
> accessible to dom0.
Ian Campbell writes ("Re: [OSSTEST PATCH 24/33] cs-adjust-flight: Provide
`jobs-del' operation"):
> On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
> > Signed-off-by: Ian Jackson
>
> Missing an update to the comment describing the sub commands provided by
> this
Ian Campbell writes ("Re: [OSSTEST PATCH 30/33] cr-daily-branch: Use
mg-adjust-flight to have smoke tests reuse builds"):
> $blessings_arg might be better than an open coded real?
>
> Oh, I see, you want to only pickup real builds, even for adhoc or play
> jobs. That makes sense. Maybe with say
On 09/18/2015 04:44 AM, Ian Campbell wrote:
On Thu, 2015-09-17 at 13:53 +0200, Mike Belopuhov wrote:
A few words here about the methodology you used to determine the names to
use would be useful to people looking back on this stuff in the future.
Also it would be sensible to CC everyone
On Fri, 2015-09-18 at 11:27 +0100, Ian Campbell wrote:
> On Fri, 2015-09-18 at 10:02 +0100, Ian Campbell wrote:
> > On Wed, 2015-09-16 at 14:07 +0100, Ian Campbell wrote:
> > > [...]
> > > +sub add_event($) {
> > > +my ($job,$reso,$type,$info,$time) = @_;
> > > +
> > > +die unless
Andrew Cooper wrote on 2015-09-18:
> On 18/09/15 12:40, Zhang, Yang Z wrote:
>> Jan Beulich wrote on 2015-09-18:
>> "Zhang, Yang Z" 09/18/15 2:29 AM >>>
Zhang, Yang Z wrote on 2015-09-08:
I have a quick check on current code. I am curious that is current
Ian,
As we discussed previously,
http://patchwork.ozlabs.org/patch/457055/
now it's time to push this into on xen/tools side since all qemu stuffs
have been merged.
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg02094.html
v4:
Ian,
Actually we had v3.5 online previously, which was
While working with qemu, IGD is a specific device in the case of pass through
so we need to identify that to handle more later. Here we define a table to
record all IGD types currently we can support. Also we need to introduce two
helper functions to get vendor and device ids to lookup that table.
On Thu, 2015-09-17 at 18:37 +0100, Ian Jackson wrote:
> This contains a very limited set of jobs
> test-amd64-amd64-libvirt
> test-amd64-amd64-xl-qemuu-debianhvm-i386
> test-armhf-armhf-xl
> and the builds they depend on.
>
> The debianhvm job exists only in this flight, and is
On Fri, Sep 18, 2015 at 3:31 PM, George Dunlap
wrote:
>> As said, me too. Perhaps we can go for option 1, which is simpler,
>> cleaner and more consistent, considering the current status of the
>> code. We can always investigate, in future, whether and how to
>>
On Fri, Sep 18, 2015 at 10:22 AM, Dario Faggioli
wrote:
> On Fri, 2015-09-18 at 00:27 -0600, Jan Beulich wrote:
>> > George Dunlap 09/17/15 4:30 PM >>>The
>
>> > > > vcpu_block()
>> >set(_VPF_blocked)
>> >v->arch.block()
>> >- Add v to
This is what the other arches do, and is what ts-host-install expects.
Signed-off-by: Ian Campbell
---
mg-debian-installer-update | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mg-debian-installer-update b/mg-debian-installer-update
index
Ian Campbell writes ("[PATCH OSSTEST] mg-debian-installer-update: download
default armhf kernel as "linux""):
> This is what the other arches do, and is what ts-host-install expects.
Acked-by: Ian Jackson
___
Xen-devel
From: Vijaya Kumar K
Emulate LPI related changes to GICR registers
Signed-off-by: Vijaya Kumar K
---
v7: - Merged patch#23 to this patch. patch#23 is just one line.
- Add 32-bit access to GICR_TYPER register
- Changed
From: Vijaya Kumar K
Helper function gic_is_lpi() is used to find
if irq is lpi or not. For GICv2 platforms this function
returns number of irq ids which represents only number of line irqs.
For GICv3 platform irq ids are calculated from nr_lpis if
HW supports
From: Vijaya Kumar K
Allocate dynamically irq descriptors for LPIs
Signed-off-by: Vijaya Kumar K
---
v6: - Add separate patch for irq_pending structures
- renamed and moved is_domain_lpi to vgic
- Updated __irq_to_domain
From: Vijaya Kumar K
Parse host dt and generate ITS node for Dom0.
ITS node resides inside GIC node so when GIC node
is encountered look for ITS node.
Signed-off-by: Vijaya Kumar K
---
v7: - Check on return value
v6: -
From: Vijaya Kumar K
Store number of lpis allocated per domain in vgic structure
Signed-off-by: Vijaya Kumar K
---
v7: - Change commit message.
- Store only nr_lpis per domain in vgic structure and drop
id_bits.
---
On Fri, 2015-09-18 at 11:50 +, Zhang, Yang Z wrote:
> Andrew Cooper wrote on 2015-09-18:
> > On 18/09/15 12:40, Zhang, Yang Z wrote:
> > > But it only happens before do vmentry. Is it possible that
> > VCPU been preempted at any time when running in hypervisor mode?
> >
> > All vcpus may be
From: Vijaya Kumar K
Change callbacks gic_host_irq_type and gic_guest_irq_type
to gic_get_host_irq_type and gic_get_guest_irq_type
in gic_hw_operations, which returns hw_irq_controller based
on irq type (SPI or LPI).
Signed-off-by: Vijaya Kumar K
From: Vijaya Kumar K
This patch introduces virtual ITS driver with following
functionality
- Introduces helper functions to manage device table and
ITT table in guest memory
- Helper function to handle virtual ITS devices assigned
to domain
From: Vijaya Kumar K
Call domain specific ITS initialization and introduce
callback in vgic for domain free
Signed-off-by: Vijaya Kumar K
---
v7: - Deprecate use of gic_lpi_supported and instead use
vgic_v3_hw.lpi_support
This run is configured for baseline tests only.
flight 37966 qemu-upstream-4.2-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/37966/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 16
From: Vijaya Kumar K
Emulate GITS* registers
Signed-off-by: Vijaya Kumar K
---
v7: - Fixed wrong usage of vgic_regN* helpers
- coding styles and comments
- GITS_BASER0 is always overwritten with new value every time
From: Vijaya Kumar K
Allocate dynamically pending_lpi descriptors for LPIs
Signed-off-by: Vijaya Kumar K
---
xen/arch/arm/vgic-v3-its.c |9 +
xen/arch/arm/vgic.c | 20 +---
From: Vijaya Kumar K
ITS translation space contains GITS_TRANSLATER register
which is written by device to raise LPI. This space needs
to mapped to every domain address space for all physical
ITS available,so that device can access GITS_TRANSLATER
register using
From: Vijaya Kumar K
Allocate and initialize irq descriptor for LPIs and
route LPIs to guest
For LPIs deactivation is not required. Hence
GICH_LR.HW is not required to set.
Signed-off-by: Vijaya Kumar K
---
v7: - Subtract 8192
From: Vijaya Kumar K
Add Virtual ITS command processing support to Virtual ITS driver
Signed-off-by: Vijaya Kumar K
---
v7: - Moved is_valid_collection() declaration to vits.h
- Added check for number of vcpus of a domain in
From: Vijaya Kumar K
Helper functions to manage its devices using RB-tree
are introduced in physical ITS driver.
This is global list of all the devices.
Signed-off-by: Vijaya Kumar K
Acked-by: Ian Campbell
From: Vijaya Kumar K
Define msi_desc structure for arm and introduce
helper functions to access msi_desc member variables.
Signed-off-by: Vijaya Kumar K
Reviewed-by: Julien Grall
---
From: Vijaya Kumar K
Introduce vgic_is_lpi_supported() helper function
to know virtual ITS availability for a domain
Signed-off-by: Vijaya Kumar K
---
v7: - its_enabled field is added to vgic structure
---
From: Vijaya Kumar K
Initialize physical ITS if HW supports LPIs.
Signed-off-by: Vijaya Kumar K
---
v7: - Export lpi support information to vgic-v3 driver from gic-v3.
- Drop gic_lpi_supported() helper function
- Add
From: Vijaya Kumar K
Enable compilation of pITS driver.
Signed-off-by: Vijaya Kumar K
From: Vijaya Kumar K
Add APIs to add devices to RB-tree, assign and remove
devices to domain.
Signed-off-by: Vijaya Kumar K
---
v7: - Added check for domain in its_assign_device() to avoid
assigning device to DomU
-
From: Vijaya Kumar K
Implement hw_irq_controller callbacks required to
handle LPIs.
Signed-off-by: Vijaya Kumar K
---
v7: - Split this patch into two. In this patch implement
only hw_irq_controller callbacks for LPIs.
v6:
From: Vijaya Kumar K
This is based on DraftG version
http://xenbits.xen.org/people/ianc/vits/draftG.pdf
Following major features are supported
- GICv3 ITS support for arm64 platform
- Only Dom0 is supported. For DomU pci passthrough feature
is required.
From: Vijaya Kumar K
NR_IRQS represents the number of lines (i.e SGIs, PPIs and SPIs).
With the introduction of LPIs, NR_IRQs is renamed to NR_ITLINES.
Similarly vgic_num_irqs() is renamed as vgic_num_irq_lines().
Signed-off-by: Vijaya Kumar K
From: Vijaya Kumar K
The linux driver is based on 4.1 with below commit id
591e5bec13f15feb13fc445b6c9c59954711c4ac
Only following code from Linux ITS driver is ported
and compiled
- LPI initialization
- ITS configuration code
- Physical command queue
1 - 100 of 123 matches
Mail list logo