flight 96220 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96220/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR.
vs. 94748
test-amd64-amd64-
On 2016/6/25 11:05, Andrew Fish wrote:
>> > On Jun 24, 2016, at 7:50 PM, Shannon Zhao wrote:
>> >
>> >
>> >
>> > On 2016/6/23 21:42, Ard Biesheuvel wrote:
> + //
> + // Get the RSDP structure address from DeviceTree
> + //
> + Status = gBS->LocateProtoc
flight 96211 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96211/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-libvirt 11 guest-startfail in 96183 pass in 96211
test-amd64-i386-libvirt-qemuu-debianh
On 2016/6/24 2:35, Julien Grall wrote:
> Hi Shannon,
>
> On 23/06/2016 04:17, Shannon Zhao wrote:
>> From: Shannon Zhao
>>
>> Add the ARM Multiboot module for ACPI, so UEFI or DomU can get the base
>> address of ACPI tables from it.
>>
>> Signed-off-by: Shannon Zhao
>> ---
>> docs/misc/arm/de
> On Jun 24, 2016, at 7:50 PM, Shannon Zhao wrote:
>
>
>
> On 2016/6/23 21:42, Ard Biesheuvel wrote:
+ //
+ // Get the RSDP structure address from DeviceTree
+ //
+ Status = gBS->LocateProtocol (&gFdtClientProtocolGuid, NULL,
>> Please add gFdtClientProtocolGuid to the
On 2016/6/23 21:42, Ard Biesheuvel wrote:
>> > + //
>> > + // Get the RSDP structure address from DeviceTree
>> > + //
>> > + Status = gBS->LocateProtocol (&gFdtClientProtocolGuid, NULL,
> Please add gFdtClientProtocolGuid to the [Depex] section of this module
>
Hi Ard,
I try to add gFdtCli
flight 96207 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96207/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-qcow2 6 xen-bootfail REGR. vs. 96178
Regressions which ar
On Fri, 2016-06-24 at 13:25 +, Wu, Feng wrote:
> >
> > Then, in this case, the reason why we are sure that all the pcpus
> > are
> > executing the body of the tasklet, is indeed the structure of
> > stop_machine_run() and stopmachine_action() themselves, which are
> > built
> > to make sure of
flight 96208 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96208/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 80927
build-i
Hi Kevin, Jan,
Thanks for comments.
On 6/24/2016 11:31 PM, Jan Beulich wrote:
On 24.06.16 at 12:56, wrote:
From: kaih.li...@gmail.com [mailto:kaih.li...@gmail.com]
Sent: Friday, June 24, 2016 6:45 PM
--- a/xen/include/asm-x86/msr-index.h
+++ b/xen/include/asm-x86/msr-index.h
@@ -133,12 +133,
flight 96202 xen-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96202/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt5 libvirt-build fail REGR. vs. 87893
build-amd64-libvi
On 06/24/16 21:48, Tamas K Lengyel wrote:
>>> {
>>> @@ -635,22 +661,22 @@ int main(int argc, char *argv[])
>>> rsp.u.mem_access = req.u.mem_access;
>>> break;
>>> case VM_EVENT_REASON_SOFTWARE_BREAKPOINT:
>>> -printf("Break
flight 96201 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96201/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64 9 debian-hvm-install fail REGR. vs.
94856
test-amd64-i3
>> {
>> @@ -635,22 +661,22 @@ int main(int argc, char *argv[])
>> rsp.u.mem_access = req.u.mem_access;
>> break;
>> case VM_EVENT_REASON_SOFTWARE_BREAKPOINT:
>> -printf("Breakpoint: rip=%016"PRIx64", gfn=%"PRIx64" (vcpu
>>
On Fri, Jun 24, 2016 at 02:02:42PM -0400, Daniel De Graaf wrote:
> On 06/24/2016 01:46 PM, Konrad Rzeszutek Wilk wrote:
> I can remove the HAS_CHECKPOLICY check completely and make the call to
> checkpolicy only conditional on the Kconfig option. I think this is
> less complicated than
On 06/24/2016 01:46 PM, Konrad Rzeszutek Wilk wrote:
I can remove the HAS_CHECKPOLICY check completely and make the call to
checkpolicy only conditional on the Kconfig option. I think this is
less complicated than stopping the compile one step above the invocation
of checkpolicy, and probably ju
> >>I can remove the HAS_CHECKPOLICY check completely and make the call to
> >>checkpolicy only conditional on the Kconfig option. I think this is
> >>less complicated than stopping the compile one step above the invocation
> >>of checkpolicy, and probably just as informative (and better, if the
>
Hello Konrad,
On 24/06/16 18:41, Konrad Rzeszutek Wilk wrote:
On Fri, Jun 24, 2016 at 01:34:29PM -0400, Daniel De Graaf wrote:
On 06/24/2016 12:50 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Jun 24, 2016 at 05:30:32PM +0100, Julien Grall wrote:
I would have expect a warning (if not an error) her
Hi Daniel,
On 24/06/16 18:34, Daniel De Graaf wrote:
On 06/24/2016 12:50 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Jun 24, 2016 at 05:30:32PM +0100, Julien Grall wrote:
diff --git a/xen/xsm/flask/Makefile b/xen/xsm/flask/Makefile
index 12fc3a9..eefd37c 100644
--- a/xen/xsm/flask/Makefile
+++ b/
On 06/24/2016 01:40 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Jun 24, 2016 at 01:34:29PM -0400, Daniel De Graaf wrote:
On 06/24/2016 12:50 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Jun 24, 2016 at 05:30:32PM +0100, Julien Grall wrote:
Hello Daniel,
Please try to CC relevant maintainers on your
On Fri, Jun 24, 2016 at 01:34:29PM -0400, Daniel De Graaf wrote:
> On 06/24/2016 12:50 PM, Konrad Rzeszutek Wilk wrote:
> >On Fri, Jun 24, 2016 at 05:30:32PM +0100, Julien Grall wrote:
> >>Hello Daniel,
> >>
> >>Please try to CC relevant maintainers on your patch. I would have missed it
> >>if Andr
On Fri, Jun 24, 2016 at 01:34:29PM -0400, Daniel De Graaf wrote:
> On 06/24/2016 12:50 PM, Konrad Rzeszutek Wilk wrote:
> >On Fri, Jun 24, 2016 at 05:30:32PM +0100, Julien Grall wrote:
> >>Hello Daniel,
> >>
> >>Please try to CC relevant maintainers on your patch. I would have missed it
> >>if Andr
On 06/24/2016 12:50 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Jun 24, 2016 at 05:30:32PM +0100, Julien Grall wrote:
Hello Daniel,
Please try to CC relevant maintainers on your patch. I would have missed it
if Andrew did not ping me on IRC.
On 20/06/16 15:04, Daniel De Graaf wrote:
This adds a
Hey all,
I think I'm ready to publicly announce a project I've been working on
for a few months called schedbench, a "microbenchmark" for schedulers
(and the Xen scheduler in particular). You can find the code, along
with a quick README, here:
https://github.com/gwd/schedbench
This is definitel
On Fri, Jun 24, 2016 at 01:44:30AM -0600, Jan Beulich wrote:
> >>> On 22.06.16 at 19:15, wrote:
> > +uint64_t cmdline_paddr = modlist[i].cmdline_paddr;
> > +
> > +if ( check_test_overlap(modlist[i].paddr, modlist[i].size) )
> > +{
> > +printf("Skipping tests due
On Fri, Jun 24, 2016 at 01:33:45AM -0600, Jan Beulich wrote:
> >>> On 22.06.16 at 19:15, wrote:
> > --- a/tools/firmware/hvmloader/hvmloader.c
> > +++ b/tools/firmware/hvmloader/hvmloader.c
> > @@ -253,10 +253,51 @@ static void acpi_enable_sci(void)
> > BUG_ON(!(pm1a_cnt_val & ACPI_PM1C_SCI_E
On Fri, Jun 24, 2016 at 05:30:32PM +0100, Julien Grall wrote:
> Hello Daniel,
>
> Please try to CC relevant maintainers on your patch. I would have missed it
> if Andrew did not ping me on IRC.
>
> On 20/06/16 15:04, Daniel De Graaf wrote:
> >This adds a Kconfig option and support for including t
On Fri, Jun 24, 2016 at 5:24 AM, Jan Beulich wrote:
On 24.06.16 at 13:20, wrote:
>>> From: Tamas K Lengyel [mailto:ta...@tklengyel.com]
>>> Sent: Friday, June 24, 2016 1:07 AM
>>>
>>> diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
>>> index 03fcba7..4b69ca6 100644
>>>
Hello Daniel,
Please try to CC relevant maintainers on your patch. I would have missed
it if Andrew did not ping me on IRC.
On 20/06/16 15:04, Daniel De Graaf wrote:
This adds a Kconfig option and support for including the XSM policy from
tools/flask/policy in the hypervisor so that the bootl
flight 96204 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96204/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 96157
Tests which
On Jun 24, 2016 05:19, "Razvan Cojocaru" wrote:
>
> On 06/24/2016 02:05 PM, George Dunlap wrote:
> > On Wed, Jun 22, 2016 at 12:38 PM, sepanta s
wrote:
> >> Hi,
> >> Is it possible to monitor the access on the pages withp2m_type_t
> >> p2m_ram_shared?
> >
> > cc'ing Tamas and Razvan
>
> Thanks fo
[Paul] inlined
-Original Message-
From: Jan Beulich [mailto:jbeul...@suse.com]
Sent: Thursday, June 23, 2016 11:19 PM
To: Lai, Paul C
Cc: Sahita, Ravi ; xen-devel
Subject: RE: [PATCH v1 Altp2m cleanup 1/3] altp2m cleanup work
>>> On 23.06.16 at 20:23, wrote:
First of all - pleas
Thanks George!
On Fri, Jun 24, 2016 at 4:37 AM, George Dunlap wrote:
> On Wed, Jun 22, 2016 at 9:16 PM, Elena Ufimtseva wrote:
>> Hello
>>
>> I am working on PCIe errors containment and XSA-124 relevant problem.
>> This is only small part of the problem and I can provide more details later
>> i
On 24/06/16 15:25, Jan Beulich wrote:
>
> And then - what's your expectation? Any parts of this new
> interface can subsequently be marked stable if we so wish. I
> don't see why this needs to happen right away.
Ok.
David
___
Xen-devel mailing list
Xe
On 07/06/16 07:31, Jan Beulich wrote:
> - drop unused function parameter of read_dev_bar()
> - drop rom_init() (now identical to bar_init())
> - fold read_dev_bar() into its now single caller
> - simplify determination of 64-bit memory resource
> - use const and unsigned
Please split this in 5 sep
On 6/21/16 12:09 PM, Daniel De Graaf wrote:
> Since enabling XSM is required to enable FLASK, place the option for
> FLASK below the one for XSM. In addition, since it does not make sense
> to enable XSM without any XSM providers, and FLASK is the only XSM
> provider, hide the option to disable FL
On 6/24/16 9:21 AM, Ponomarenko Andrey wrote:
> Hello,
>
> I maintain a new project for backward compatibility analysis of the Linux
> ABIs. The report for Xen base libraries has been recently added to the
> project: http://abi-laboratory.pro/tracker/timeline/xen/
>
> The report is generated da
On Fri, 2016-06-24 at 14:49 +0100, George Dunlap wrote:
> On 24/06/16 14:42, Wu, Feng wrote:
> > Here is my understanding, if the guest has nothing to do, it will
> > call HLT, and Xen hypervisor will call vcpu_block(), if we don't
> > block the vCPU and return to guest, guest will continue to run
On 24/06/16 15:25, Jan Beulich wrote:
On 24.06.16 at 15:51, wrote:
>> On 24/06/16 14:37, Jan Beulich wrote:
>> On 24.06.16 at 15:27, wrote:
On 24/06/16 11:35, Jan Beulich wrote:
On 24.06.16 at 12:29, wrote:
>> On 24/06/16 11:21, Jan Beulich wrote:
>>> A long while
>>> On 24.06.16 at 15:51, wrote:
> On 24/06/16 14:37, Jan Beulich wrote:
> On 24.06.16 at 15:27, wrote:
>>> On 24/06/16 11:35, Jan Beulich wrote:
>>> On 24.06.16 at 12:29, wrote:
> On 24/06/16 11:21, Jan Beulich wrote:
>> A long while back separating out all control kind operatio
Hello,
I maintain a new project for backward compatibility analysis of the Linux ABIs.
The report for Xen base libraries has been recently added to the project:
http://abi-laboratory.pro/tracker/timeline/xen/
The report is generated daily with the help of the abi-compliance-checker,
abi-dumper
On Fri, Jun 24, 2016 at 01:23:19AM -0600, Jan Beulich wrote:
> >>> On 22.06.16 at 19:15, wrote:
> > --- a/tools/libxl/libxl_paths.c
> > +++ b/tools/libxl/libxl_paths.c
> > @@ -35,6 +35,16 @@ const char *libxl__run_dir_path(void)
> > return XEN_RUN_DIR;
> > }
> >
> > +const char *libxl__sea
flight 96196 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96196/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR.
vs. 94748
test-amd64-amd64-
On 24/06/16 10:13, Jan Beulich wrote:
> Reads following writes with all address bits set to 1 should return all
> changeable address bits as one, not the BAR size (nor, as was the case
> for the upper half of 64-bit BARs, the high half of the region's end
> address). Presumably this didn't cause an
On 24/06/16 14:58, Julien Grall wrote:
> Hi Stefano,
>
> On 23/06/16 15:14, Stefano Stabellini wrote:
>> On Tue, 21 Jun 2016, Julien Grall wrote:
>>> The prototype and the declaration of p2m_lookup disagree on how the
>>> function should be used. One expect a frame number whilst the other
>>> an ad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-4.7b-rc4-tag
xen: bug fixes for 4.7-rc4
- - Fix x86 PV dom0 crash during early boot on some hardware.
- - Fix two pciback bugs affects
Hi Stefano,
On 23/06/16 15:14, Stefano Stabellini wrote:
On Tue, 21 Jun 2016, Julien Grall wrote:
The prototype and the declaration of p2m_lookup disagree on how the
function should be used. One expect a frame number whilst the other
an address.
Thankfully, everyone is using with an address to
On 24/06/16 14:37, Jan Beulich wrote:
On 24.06.16 at 15:27, wrote:
>> On 24/06/16 11:35, Jan Beulich wrote:
>> On 24.06.16 at 12:29, wrote:
On 24/06/16 11:21, Jan Beulich wrote:
> A long while back separating out all control kind operations (intended
> for use by only the co
On 24/06/16 14:42, Wu, Feng wrote:
>
>
>> -Original Message-
>> From: Dario Faggioli [mailto:dario.faggi...@citrix.com]
>> Sent: Friday, June 24, 2016 6:29 PM
>> To: Wu, Feng ; xen-devel@lists.xen.org
>> Cc: k...@xen.org; Tian, Kevin ; jbeul...@suse.com;
>> andrew.coop...@citrix.com; geor
flight 96214 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96214/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
> -Original Message-
> From: Dario Faggioli [mailto:dario.faggi...@citrix.com]
> Sent: Friday, June 24, 2016 6:29 PM
> To: Wu, Feng ; xen-devel@lists.xen.org
> Cc: k...@xen.org; Tian, Kevin ; jbeul...@suse.com;
> andrew.coop...@citrix.com; george.dun...@eu.citrix.com;
> konrad.w...@oracle
>>> On 24.06.16 at 15:27, wrote:
> On 24/06/16 11:35, Jan Beulich wrote:
> On 24.06.16 at 12:29, wrote:
>>> On 24/06/16 11:21, Jan Beulich wrote:
A long while back separating out all control kind operations (intended
for use by only the control domain or device model) from the curre
On 24/06/16 11:35, Jan Beulich wrote:
On 24.06.16 at 12:29, wrote:
>> On 24/06/16 11:21, Jan Beulich wrote:
>>> A long while back separating out all control kind operations (intended
>>> for use by only the control domain or device model) from the currect
>>> hvmop hypercall has been discusse
> > Thanks for your replay. Yes, I think this is point. Here descheduling
> > of vCPU3
> > happens, and the reason we will choose the tasklet as the next
> > running
> > unit for sure (not choosing another vCPU or vCPU3 itself as the next
> > running unit) is because tasklet will overrides all othe
>>> On 24.06.16 at 13:55, wrote:
>> --- a/xen/drivers/passthrough/pci.c
>> +++ b/xen/drivers/passthrough/pci.c
>> @@ -419,7 +419,7 @@ static void free_pdev(struct pci_seg *pseg, struct
>> pci_dev *pdev)
>> xfree(pdev);
>> }
>>
>> -static void _pci_hide_device(struct pci_dev *pdev)
>> +void
> From: Xu, Quan
> Sent: Friday, June 24, 2016 1:52 PM
>
> From: Quan Xu
>
> If Device-TLB flush timed out, we hide the target ATS device
> immediately and crash the domain owning this ATS device. If
> impacted domain is hardware domain, just throw out a warning.
>
> By hiding the device, we ma
> From: Xu, Quan
> Sent: Friday, June 24, 2016 1:52 PM
>
> From: Quan Xu
>
> Signed-off-by: Quan Xu
>
> CC: Julien Grall
> CC: Kevin Tian
> CC: Feng Wu
> CC: Jan Beulich
> CC: Suravee Suthikulpanit
> ---
> xen/drivers/passthrough/iommu.c | 30
> --
> xen/d
> From: Xu, Quan
> Sent: Friday, June 24, 2016 1:52 PM
>
> From: Quan Xu
>
> a struct pci_dev* instead of SBDF is stored inside struct
> pci_ats_dev and parameter to enable_ats_device().
>
> Signed-off-by: Quan Xu
Can we unify the naming convention throughout the patch, e.g.
always using ats
On Wed, Jun 22, 2016 at 9:16 PM, Elena Ufimtseva wrote:
> Hello
>
> I am working on PCIe errors containment and XSA-124 relevant problem.
> This is only small part of the problem and I can provide more details later
> if that is of someone's interest.
> As the temporary solution, guest domain with
On Fri, Jun 24, 2016 at 3:45 AM, Dario Faggioli
wrote:
> On Thu, 2016-06-23 at 11:42 +0100, George Dunlap wrote:
>> On 22/06/16 17:16, Meng Xu wrote:
>> >
>> > I think he is trying to align those comments to make them start
>> > from
>> > the same column. I was confused at the reason at the very
>
> From: Xu, Quan
> Sent: Friday, June 24, 2016 1:52 PM
>
> From: Quan Xu
>
> QI ought to have got disabled if any of the IOMMU table setup
> failed. A QI function (other than enable_qinval) is unreachable
> when qi_ctrl->qinval_maddr is zero.
>
> Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Commit "8156d48 pc: allow raising low memory via max-ram-below-4g
option" causes a regression on xen, because it uses a different
memory split.
This patch initializes max-ram-below-4g to zero and leaves the
initialization to the memory initialization functions. That way
they can pick different de
On Fri, Jun 24, 2016 at 12:09:53PM +0100, George Dunlap wrote:
> On Wed, Jun 22, 2016 at 6:28 PM, Anthony PERARD
> wrote:
> > This only implement a simpler non-nested brace expansion.
> >
> > This will convert brace expansion style use in MAINTAINER into a regex
> > that get_maintainer.pl can use
> From: Xu, Quan
> Sent: Friday, June 24, 2016 1:52 PM
>
> From: Quan Xu
>
> Today we do Device-TLB flush synchronization after issuing flush
> requests for all ATS devices belonging to a VM. Doing so however
> imposes a limitation, i.e. that we can not figure out which flush
> request is blocke
>>> On 24.06.16 at 12:56, wrote:
>> From: kaih.li...@gmail.com [mailto:kaih.li...@gmail.com]
>> Sent: Friday, June 24, 2016 6:45 PM
>> --- a/xen/include/asm-x86/msr-index.h
>> +++ b/xen/include/asm-x86/msr-index.h
>> @@ -133,12 +133,13 @@
>> #define MSR_IA32_VMX_TRUE_EXIT_CTLS 0x48f
> From: Xu, Quan
> Sent: Friday, June 24, 2016 1:52 PM
>
> From: Quan Xu
>
> The parameter 'iommu_dev_iotlb_timeout' specifies the timeout
> of device IOTLB invalidation in milliseconds. By default, the
> timeout is 1000 milliseconds, which can be boot-time changed.
>
> We also confirmed with V
>>> On 24.06.16 at 13:20, wrote:
>> From: Tamas K Lengyel [mailto:ta...@tklengyel.com]
>> Sent: Friday, June 24, 2016 1:07 AM
>>
>> diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
>> index 03fcba7..4b69ca6 100644
>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>> +++ b/xen/arch/x86/hvm/
> From: Tamas K Lengyel [mailto:ta...@tklengyel.com]
> Sent: Friday, June 24, 2016 1:07 AM
>
> diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
> index 03fcba7..4b69ca6 100644
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -3373,10 +3373,39 @@ void v
On 06/24/2016 02:05 PM, George Dunlap wrote:
> On Wed, Jun 22, 2016 at 12:38 PM, sepanta s wrote:
>> Hi,
>> Is it possible to monitor the access on the pages withp2m_type_t
>> p2m_ram_shared?
>
> cc'ing Tamas and Razvan
Thanks for the CC. Judging by the "if ( npfec.write_access && (p2mt ==
p2m_r
On Fri, Jun 24, 2016 at 07:46:23AM +0200, Gerd Hoffmann wrote:
> On Do, 2016-06-23 at 17:18 +0100, Anthony PERARD wrote:
> > On Thu, Jun 23, 2016 at 04:57:54PM +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > How could xen_ram_init() find out if the value of max-ram-below-4g is
> > > > the de
On Wed, Jun 22, 2016 at 6:28 PM, Anthony PERARD
wrote:
> This only implement a simpler non-nested brace expansion.
>
> This will convert brace expansion style use in MAINTAINER into a regex
> that get_maintainer.pl can use to match a path again a maintainer
> section.
>
> It is done by using two d
On Wed, Jun 22, 2016 at 12:38 PM, sepanta s wrote:
> Hi,
> Is it possible to monitor the access on the pages withp2m_type_t
> p2m_ram_shared?
cc'ing Tamas and Razvan
-George
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-
> From: Tamas K Lengyel [mailto:ta...@tklengyel.com]
> Sent: Friday, June 24, 2016 1:07 AM
>
> The return value has not been clearly defined, with the function
> never returning 0 which seemingly indicated a condition where the
> guest should crash.
>
> In this patch we define -rc as error condit
> From: Tamas K Lengyel [mailto:ta...@tklengyel.com]
> Sent: Saturday, June 18, 2016 3:09 AM
>
> On Thu, Jun 2, 2016 at 4:52 PM, Tamas K Lengyel wrote:
> > The return value has not been clearly defined, with the function
> > never returning 0 which seemingly indicated a condition where the
> > gu
flight 96188 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96188/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail in
96161 pass in 96188
test-amd64-amd6
> From: kaih.li...@gmail.com [mailto:kaih.li...@gmail.com]
> Sent: Friday, June 24, 2016 6:45 PM
>
> From: Kai Huang
>
> Below commit introduced a new macro MSR_IA32_FEATURE_CONTROL for
> IA32_FEATURE_CONTROL MSR but it didn't remove old IA32_FEATURE_CONTROL_MSR
> macro. The new one has better n
From: Kai Huang
Below commit introduced a new macro MSR_IA32_FEATURE_CONTROL for
IA32_FEATURE_CONTROL MSR but it didn't remove old IA32_FEATURE_CONTROL_MSR
macro. The new one has better naming convention, so remove the old as
duplication and replace the relevant code with new one.
mwait-idle
flight 96210 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/96210/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 96189
Tests which di
On 6/22/2016 11:44 PM, Jan Beulich wrote:
On 22.06.16 at 12:17, wrote:
@@ -288,7 +289,6 @@
#define MSR_IA32_PLATFORM_ID 0x0017
#define MSR_IA32_EBL_CR_POWERON0x002a
#define MSR_IA32_EBC_FREQUENCY_ID 0x002c
-#define MSR_IA32_FEATURE_CONTROL 0
>>> On 24.06.16 at 12:29, wrote:
> On 24/06/16 11:21, Jan Beulich wrote:
>> A long while back separating out all control kind operations (intended
>> for use by only the control domain or device model) from the currect
>> hvmop hypercall has been discussed. This series aims at finally making
>> th
Since injection works on a remote vCPU, and since there's no
enforcement of the subject vCPU being paused, there's a potential race
between the producing and consuming sides. Fix this by leveraging the
vector field as synchronization variable.
Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
Note that we can't adjust HVM_IOREQSRV_BUFIOREQ_* to properly obey
name space rules, as these constants as in use by callers of the libxc
interface.
Signed-off-by: Jan Beulich
Reviewed-by: Wei Liu
Reviewed-by: Paul Durrant
Reviewed-by: Andrew Cooper
--- a/tools/libxc/include/xenctrl.h
+++ b/t
Signed-off-by: Jan Beulich
Reviewed-by: Wei Liu
Reviewed-by: Andrew Cooper
--- a/tools/libxc/xc_misc.c
+++ b/tools/libxc/xc_misc.c
@@ -508,27 +508,11 @@ int xc_hvm_set_pci_link_route(
int xc_hvm_inject_msi(
xc_interface *xch, domid_t dom, uint64_t addr, uint32_t data)
{
-DECLARE_HYPE
Signed-off-by: Jan Beulich
Reviewed-by: Wei Liu
Reviewed-by: Andrew Cooper
--- a/tools/libxc/xc_misc.c
+++ b/tools/libxc/xc_misc.c
@@ -584,31 +584,15 @@ int xc_hvm_inject_trap(
uint32_t type, uint32_t error_code, uint32_t insn_len,
uint64_t cr2)
{
-DECLARE_HYPERCALL_BUFFER(struct
This allows elimination of the (ab)use of the high operation number
bits for encoding continuations.
Also limiting "nr" at the libxc level to 32 bits (the high 32 bits of
the previous 64-bit parameter got ignore so far).
Signed-off-by: Jan Beulich
Reviewed-by: Wei Liu
Reviewed-by: Andrew Cooper
Also limiting "nr" at the libxc level to 32 bits (the high 32 bits of
the previous 64-bit parameter got ignore so far).
Signed-off-by: Jan Beulich
Reviewed-by: Wei Liu
Reviewed-by: Andrew Cooper
--- a/tools/libxc/include/xenctrl.h
+++ b/tools/libxc/include/xenctrl.h
@@ -1613,7 +1613,7 @@ int x
Also limiting "nr" at the libxc level to 32 bits (the high 32 bits of
the previous 64-bit parameter got ignore so far).
Signed-off-by: Jan Beulich
Reviewed-by: Wei Liu
Reviewed-by: Andrew Cooper
--- a/tools/libxc/include/xenctrl.h
+++ b/tools/libxc/include/xenctrl.h
@@ -1620,7 +1620,7 @@ int x
Note that this retains the hvmop interface definitions as those had
(wrongly) been exposed to non-tool stack consumers (albeit the
operation wouldn't have succeeded when requested by a domain for
itself).
Signed-off-by: Jan Beulich
Reviewed-by: Wei Liu
Reviewed-by: Andrew Cooper
--- a/tools/li
On 24/06/16 11:21, Jan Beulich wrote:
> A long while back separating out all control kind operations (intended
> for use by only the control domain or device model) from the currect
> hvmop hypercall has been discussed. This series aims at finally making
> this reality (at once allowing to streamli
Hi,
Ping?
Cheers,
On 14/06/16 12:50, Julien Grall wrote:
The helper iomem_access_permitted expects MFNs in parameters and not
GNFs. Thankfully only the hardware domain can call this function and
it will always be with GFNS == MFNs for now.
Also, fix the printf to use the MFN range and not the
Note that this retains the hvmop interface definitions as those had
(wrongly) been exposed to non-tool stack consumers (albeit the
operation wouldn't have succeeded when requested by a domain for
itself).
Signed-off-by: Jan Beulich
Reviewed-by: Wei Liu
Reviewed-by: Andrew Cooper
--- a/tools/li
On Fri, 2016-06-24 at 06:33 +, Wu, Feng wrote:
> > -Original Message-
> > From: Dario Faggioli [mailto:dario.faggi...@citrix.com]
> > In your case, AFAICUI, it's:
> > - the vCPU should block, waiting for an event
> > - the event is _not_ arrived, so we indeed should block
> > - we do
Note that this adds validation of the "domain" interface structure
field, which previously got ignored.
Note further that this retains the hvmop interface definitions as those
had (wrongly) been exposed to non-tool stack consumers (albeit the
operation wouldn't have succeeded when requested by a d
>>> On 24.06.16 at 11:57, wrote:
> On 6/24/2016 4:01 PM, Jan Beulich wrote:
> On 24.06.16 at 09:12, wrote:
>>> On 6/24/2016 2:12 PM, Jan Beulich wrote:
And then, thinking about it again especially in the context of
the hvmctl series - the unbinding of the type is happening in a
On Fri, 2016-06-24 at 07:59 +, Wu, Feng wrote:
> > -Original Message-
> > From: Dario Faggioli [mailto:dario.faggi...@citrix.com]
> > So, vCPU 3 was running, but then some called stop_machine_run(),
> > which
> > causes the descheduling of vCPU 3, and the execution of the
> > stopmachin
... as a means to replace all HVMOP_* which a domain can't issue on
itself (i.e. intended for use by only the control domain or device
model).
Signed-off-by: Jan Beulich
Reviewed-by: Wei Liu
---
v2: Widen cmd field to 32 bits and opaque one to 64. Drop
HVMCTL_iter_*.
--- a/xen/arch/x86/hvm/
On Tue, Jun 21, 2016 at 5:04 PM, Paul Lai wrote:
> Move altp2m specific functions to altp2m files. This makes the code
> a little easier to read.
>
> Signed-off-by: Paul Lai
> ---
> xen/arch/x86/mm/altp2m.c | 43
> +++
> xen/arch/x86/mm/hap/hap.c
A long while back separating out all control kind operations (intended
for use by only the control domain or device model) from the currect
hvmop hypercall has been discussed. This series aims at finally making
this reality (at once allowing to streamline the associated XSM checking).
01: public /
On Mon, Jun 20, 2016 at 9:00 AM, Fadwa Messaoudi
wrote:
> Hi,
> is it possible to install Xen on QEMU , and if so could you send me a
> details tutorial on how to do it.
Did you try it?
Also, you might want to read this:
http://wiki.xenproject.org/wiki/Asking_Developer_Questions
Good luck,
-G
On 6/24/2016 4:01 PM, Jan Beulich wrote:
On 24.06.16 at 09:12, wrote:
On 6/24/2016 2:12 PM, Jan Beulich wrote:
In any event, I think log-dirty shouldn't be disabled when an
ioreq server binds the type, but as long as there are outstanding
entries of that type. That way, the "cannot be migrat
1 - 100 of 119 matches
Mail list logo
