All,
we're seeing recurring but intermittent failures in osstest on just the
two hosts using these particular CPU types. The closest similar ones,
using Xeon E5-2407 v2, do not exhibit this same behavior. We do
note that the latter run at microcode level 0x427, while the problem
ones are only at 0
flight 58355 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58355/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail in 58306 REGR. vs. 57312
Tests which are faili
>>> On 10.06.15 at 19:22, wrote:
> On Wed, Jun 10, 2015 at 2:37 AM, Jan Beulich wrote:
> On 10.06.15 at 11:26, wrote:
>>> On Wed, 2015-06-10 at 10:15 +0100, Jan Beulich wrote:
>>> On 10.06.15 at 10:56, wrote:
> On Tue, 2015-06-09 at 14:53 +0100, Jan Beulich wrote:
>> From: Ko
> -Original Message-
> From: Ian Jackson [mailto:ian.jack...@eu.citrix.com]
> Sent: Wednesday, June 10, 2015 11:46 PM
> To: Pang, LongtaoX
> Cc: xen-devel@lists.xen.org; ian.campb...@citrix.com; wei.l...@citrix.com; Hu,
> Robert
> Subject: Re: [OSSTEST Nested PATCH v11 7/7] Add test job f
> -Original Message-
> From: Ian Jackson [mailto:ian.jack...@eu.citrix.com]
> Sent: Wednesday, June 10, 2015 9:59 PM
> To: Pang, LongtaoX
> Cc: xen-devel@lists.xen.org; ian.campb...@citrix.com; wei.l...@citrix.com; Hu,
> Robert
> Subject: Re: [OSSTEST Nested PATCH v11 5/7] Add new script
> -Original Message-
> From: Ian Jackson [mailto:ian.jack...@eu.citrix.com]
> Sent: Wednesday, June 10, 2015 9:41 PM
> To: Pang, LongtaoX
> Cc: xen-devel@lists.xen.org; ian.campb...@citrix.com; wei.l...@citrix.com; Hu,
> Robert
> Subject: Re: [OSSTEST Nested PATCH v11 4/7] Changes on test
On 10/06/15 20:41, Ed White wrote:
> On 06/10/2015 11:23 AM, Andrew Cooper wrote:
>> On 10/06/15 01:09, Ed White wrote:
>>> This document describes a new capability for VM Introspection, Security and
>>> Privacy in Xen. The new capability is called “altp2m” (short for Alternate
>>> p2m) that is u
On Wed, Jun 10, Julien Grall wrote:
> There is also a variable MAX_CPUS defined to 256. which is used every.
You are right, while forwarding an old patch (from memory) I changed the
wrong place. MAX_CPUS is already at 256 so no change is strictly
neccessary.
I suggest to drop that patch from thi
Hello all,
I will be writing a xen front and back-end pair for a 9p
transport. I have two areas where I'm still a little more muddled than
I'd like to be.
Can anyone please recommend a good article on either grant tables
or the handshaking between the front and back-end drivers, or bot
Hi Dario,
First I think I got most of the points you raised/explained! They are
very very clear and thanks for the detailed explanation of your idea!
I have some minor questions about your comments/advices.
>
>> 2015-06-09 5:53 GMT-07:00 Dario Faggioli :
>
>> > Thanks for doing this. The first q
Commit 709294226f7f ("mm: provide early_memremap_ro to establish
read-only mapping") broke building on some architectures like arm32 by
requiring PAGE_KERNEL_RO. On architectures with that macro not defined
fall back to R/W mappings.
Signed-off-by: Juergen Gross
---
include/asm-generic/fixmap.h
On Wed, 2015-06-10 at 14:30 +0100, Ian Jackson wrote:
> longtao.pang writes ("[OSSTEST Nested PATCH v11 2/7] Parsing grub which has
> 'submenu' primitive"):
> > Now auto-gen kernel grub2 config file's boot menu entries can have
> > 2-level hierarchy, containing 'submenu' primitive, which is compri
On 06/10/2015 11:18 PM, Ian Campbell wrote:
> On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wrote:
>> From: Wen Congyang
>>
>> For PVHVM, the hypercall return code is 0, and it can be resumed
>> in a new domain context.
>> we suspend PVHVM and resume it is like this:
>> 1. suspend it via evtchn
flight 58354 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58354/
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.
58167
test-armhf-armhf
On 06/10/2015 11:37 PM, Ian Campbell wrote:
On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wrote:
From: Wen Congyang
The guest is paused after libxl_domain_create_restore().
Secondary vm is running in colo mode. So we need to unpause
the guest. The current API libxl_domain_unpause() is
not
On 06/10/2015 10:55 PM, Ian Campbell wrote:
On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wrote:
If the err is RECORD_NOT_PROCESSED, and it is an optional record,
restore will still fail. The patch fix this.
Whichever approach you take to fixing this, please say _how_ the change
fixes it,
On 06/10/2015 11:35 PM, Ian Campbell wrote:
On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wrote:
Secondary vm is running in colo mode. So we will do
the following things again and again:
1. suspend both primay vm and secondary vm
2. sync the state
3. resume both primary vm and secondary vm
On 06/10/2015 11:20 PM, Ian Campbell wrote:
On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wrote:
When we are under COLO, we will send dirty page bitmap info from
secondary to primary at every checkpoint.
... and this is a _libxl_ operation? Is that the right layer here?
For the first qu
Before we refine RMRR mechanism, USB RMRR may conflict with guest bios
region so we always ignore USB RMRR. Now this can be gone when we enable
pci_force to check/reserve RMRR.
Signed-off-by: Tiejun Chen
---
xen/drivers/passthrough/vtd/dmar.h | 1 -
xen/drivers/passthrough/vtd/iommu.c | 11 ++-
This patch passes our rdm reservation policy inside libxl
when we assign a device or attach a device.
Signed-off-by: Tiejun Chen
---
docs/man/xl.pod.1 | 7 ++-
tools/libxl/libxl_pci.c | 10 +-
tools/libxl/xl_cmdimpl.c | 23 +++
tools/libxl/xl_cmdtable.
Here we'll construct a basic guest e820 table via
XENMEM_set_memory_map. This table includes lowmem, highmem
and RDMs if they exist. And hvmloader would need this info
later.
Signed-off-by: Tiejun Chen
---
tools/libxl/libxl_dom.c | 5 +++
tools/libxl/libxl_internal.h | 24 ++
t
Now we can use that memory map to build our final
e820 table but it may need to reorder all e820
entries.
Signed-off-by: Tiejun Chen
---
tools/firmware/hvmloader/e820.c | 62 +++--
1 file changed, 48 insertions(+), 14 deletions(-)
diff --git a/tools/firmware/
While building a VM, HVM domain builder provides struct hvm_info_table{}
to help hvmloader. Currently it includes two fields to construct guest
e820 table by hvmloader, low_mem_pgend and high_mem_pgend. So we should
check them to fix any conflict with RAM.
RMRR can reside in address space beyond 4
This patch passes rdm reservation policy to xc_assign_device() so the policy
is checked when assigning devices to a VM.
Signed-off-by: Tiejun Chen
---
tools/libxc/include/xenctrl.h | 3 ++-
tools/libxc/xc_domain.c | 6 +-
tools/libxl/libxl_pci.c | 3 ++-
tool
When allocating mmio address for PCI bars, we need to make
sure they don't overlap with reserved regions.
Signed-off-by: Tiejun Chen
---
tools/firmware/hvmloader/pci.c | 36 ++--
1 file changed, 34 insertions(+), 2 deletions(-)
diff --git a/tools/firmware/hvmload
Currently we're intending to cover this kind of devices
with shared RMRR simply since the case of shared RMRR is
a rare case according to our previous experiences. But
late we can group these devices which shared rmrr, and
then allow all devices within a group to be assigned to
same domain.
Signed
We will introduce the hypercall xc_reserved_device_memory_map
approach to libxc. This helps us get rdm entry info according to
different parameters. If flag == PCI_DEV_RDM_ALL, all entries
should be exposed. Or we just expose that rdm entry specific to
a SBDF.
Signed-off-by: Tiejun Chen
---
tool
This patch introduces user configurable parameters to specify RDM
resource and according policies,
Global RDM parameter:
rdm = "type=none/host,reserve=strict/relaxed"
Per-device RDM parameter:
pci = [ 'sbdf, rdm_reserve=strict/relaxed' ]
Global RDM parameter, "type", allows user to specif
We will create this sort of identity mapping as follows:
If the gfn space is unoccupied, we just set the mapping. If the space
is already occupied by 1:1 mappings, do nothing. Failed for any
other cases.
Signed-off-by: Tiejun Chen
---
xen/arch/x86/mm/p2m.c | 35 +
Now we get this map layout by call XENMEM_memory_map then
save them into one global variable memory_map[]. It should
include lowmem range, rdm range and highmem range. Note
rdm range and highmem range may not exist in some cases.
And here we need to check if any reserved memory conflicts with
[RES
v3:
* Rearrange all patches orderly as Wei suggested
* Rebase on the latest tree
* Address some Wei's comments on tools side
* Two changes for runtime cycle
patch #2,xen/x86/p2m: introduce set_identity_p2m_entry, on hypervisor side
a>. Introduce paging_mode_translate()
Otherwise, we'll see
This patch enables XENMEM_memory_map in hvm. So we can use it to
setup the e820 mappings.
Signed-off-by: Tiejun Chen
Reviewed-by: Tim Deegan
---
xen/arch/x86/hvm/hvm.c | 2 --
xen/arch/x86/mm.c | 6 --
2 files changed, 8 deletions(-)
diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/
From: Jan Beulich
This is a prerequisite for punching holes into HVM and PVH guests' P2M
to allow passing through devices that are associated with (on VT-d)
RMRRs.
Signed-off-by: Jan Beulich
Signed-off-by: Tiejun Chen
---
xen/common/compat/memory.c | 66 +
RMRR reserved regions must be setup in the pfn space with an identity
mapping to reported mfn. However existing code has problem to setup
correct mapping when VT-d shares EPT page table, so lead to problem
when assigning devices (e.g GPU) with RMRR reported. So instead, this
patch aims to setup ide
This patch extends the existing hypercall to support rdm reservation policy.
We return error or just throw out a warning message depending on whether
the policy is "strict" or "relaxed" when reserving RDM regions in pfn space.
Note in some special cases, e.g. add a device to hwdomain, and remove a
On 06/10/2015 07:47 PM, Paul Durrant wrote:
>> -Original Message-
>> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
>> boun...@lists.xen.org] On Behalf Of Wen Congyang
>> Sent: 10 June 2015 12:38
>> To: Paul Durrant; Andrew Cooper; Yang Hongyang; xen-devel@lists.xen.org
>> Cc: Wei
On Wed, 2015-06-10 at 19:15 +, osstest service user wrote:
> flight 58330 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/58330/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-armhf-armhf-xl-c
flight 58344 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58344/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail REGR. vs. 56492
test-amd64-i386-xl-qemuu-ovm
flight 58342 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58342/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl 9 debian-install fail REGR. vs. 52209-bisect
test-amd64-amd64-pair
On 06/10/2015 04:09 PM, Andrew Cooper wrote:
> On 10/06/15 20:41, Ed White wrote:
>> On 06/10/2015 11:23 AM, Andrew Cooper wrote:
>>> On 10/06/15 01:09, Ed White wrote:
This document describes a new capability for VM Introspection, Security
and Privacy in Xen. The new capability is calle
Hi Olaf,
On 09/06/2015 07:07, Olaf Hering wrote:
And now that I enabled build also for sles12-aarch64 an old error is
still present in that base system:
In file included from
/home/abuild/rpmbuild/BUILD/xen-4.6.30993/non-dbg/tools/xenstore/../../tools/include/xen/xen.h:35:0,
No HTML, please.
On Wed, 2015-06-10 at 00:18 -0400, Dagaen Golomb wrote:
> And note that, when I say "timer", I mean an actual Xen timer,
> i.e.,
> those things that are started, stopped, and with a timer
> handling
> routine being called when they expire.
flight 58333 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58333/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 15
rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 581
Hi Julien,
>> A simple "export CONFIG_DTB_FILE=...".
>
>Are you using an absolute path?
Absolute path, yes.
>> So your patch isn't designed to help in this case (CNTFRQ set on core 0
>> only, no clock-frequency property in timer node of DT).
>
>Well, my patch is designed to propagate the "clock
On 10/06/2015 19:55, Konrad Rzeszutek Wilk wrote:
>> All other processor registers and flag bits are undefined. The OS is in
>> charge of setting up it's own stack, GDT and IDT.
>>
>> Note that the boot protocol resembles the multiboot1 specification,
>> this is done so OSes with multiboot1 entry
Currently only QEMU traditional supports stubdom and we want to
eventually do away with non-XSM test cases, so we only create
test-amd64-{i386,amd64}-xl-qemut-stubdom-debianhvm-amd64-xsm
Note that stubdom only supports serial='pty'. Piping serial to stderr
causes stubdom to exit abnormally.
Si
Signed-off-by: Wei Liu
---
Osstest/TestSupport.pm | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm
index 1f3bab2..853631c 100644
--- a/Osstest/TestSupport.pm
+++ b/Osstest/TestSupport.pm
@@ -90,7 +90,7 @@ BEGIN {
Hi,
On 10/06/2015 08:45, Ian Campbell wrote:
4. DomU access / assignment PCI device
--
When a device is attached to a domU, provision has to be made such that
it can
access the MMIO space of the device and xen is able to identify the mapping
between guest bdf
Hi Olaf,
On 09/06/2015 07:23, Olaf Hering wrote:
To match the hypervisor default which was introduced in
9da0c5b63933b9912e3903190601661813954d0d, bump the limit.
Signed-off-by: Olaf Hering
Acked-by: George Dunlap
Acked-by: Wei Liu
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
C
On Tue, Jun 02, 2015 at 04:48:25PM +0100, Malcolm Crossley wrote:
> On 02/06/15 15:34, Konrad Rzeszutek Wilk wrote:
> > On Tue, Jun 02, 2015 at 11:06:26AM +0100, Malcolm Crossley wrote:
> >> On 01/06/15 18:55, Konrad Rzeszutek Wilk wrote:
> >>> On Mon, Jun 01, 2015 at 05:03:14PM +0100, Malcolm Cros
On Fri, Jun 05, 2015 at 05:29:21PM +0100, Ian Campbell wrote:
> On Wed, 2015-06-03 at 09:35 -0400, Boris Ostrovsky wrote:
> > > What I'm hearing from the x86 maintainers is that this is actually a
> > > high priority and not a "nice to have cleanup".
> > >
> > >> I picked 32-bit support, Elena is l
On Wed, Jun 10, 2015 at 11:12 AM, Andrew Cooper
wrote:
> On 10/06/15 18:22, Roy Franz wrote:
>>
I read it backwards and thought this was currently excluding them like
x86 does.
Am I correct that the stricter x86 behaviour is per the spec, and this
new option is a workaroun
On 10/06/15 20:48, Konrad Rzeszutek Wilk wrote:
> On Wed, Jun 10, 2015 at 07:12:07PM +0100, Andrew Cooper wrote:
>> On 10/06/15 18:22, Roy Franz wrote:
> I read it backwards and thought this was currently excluding them like
> x86 does.
>
> Am I correct that the stricter x86 behavio
flight 58334 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58334/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-libvirt 11 guest-start fail blocked in 56585-bisect
test-amd64-amd64-libvirt 11 gu
On Wed, Jun 10, 2015 at 07:12:07PM +0100, Andrew Cooper wrote:
> On 10/06/15 18:22, Roy Franz wrote:
> >
> >>> I read it backwards and thought this was currently excluding them like
> >>> x86 does.
> >>>
> >>> Am I correct that the stricter x86 behaviour is per the spec, and this
> >>> new option i
From: Konrad Rzeszutek Wilk
For a passthrough device we maintain a state of emulated
registers value contained within d->config. We also consult
the host registers (and apply ro and write masks) whenever
the guest access the registers. This is done in xen_pt_pci_write_config
and xen_pt_pci_read_c
On 06/10/2015 11:23 AM, Andrew Cooper wrote:
> On 10/06/15 01:09, Ed White wrote:
>> This document describes a new capability for VM Introspection, Security and
>> Privacy in Xen. The new capability is called “altp2m” (short for Alternate
>> p2m) that is used to provide the ability for Xen to hos
Wei Liu (2):
TestSupport: introduce guest_var_boolean
Stubdom test case
Osstest/TestSupport.pm | 16 ++--
make-flight| 16 ++--
ts-debian-hvm-install | 3 +++
3 files changed, 31 insertions(+), 4 deletions(-)
--
1.9.1
_
On 10/06/15 01:09, Ed White wrote:
> This document describes a new capability for VM Introspection, Security and
> Privacy in Xen. The new capability is called “altp2m” (short for Alternate
> p2m) that is used to provide the ability for Xen to host alternate guest
> physical memory domains for a
flight 58330 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58330/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail REGR. vs. 58264
Regressions which ar
On 10/06/15 18:22, Roy Franz wrote:
>
>>> I read it backwards and thought this was currently excluding them like
>>> x86 does.
>>>
>>> Am I correct that the stricter x86 behaviour is per the spec, and this
>>> new option is a workaround for non-compliant systems?
>> Yes.
>>
>>> If so unless Roy kno
On Wed, Jun 10, 2015 at 02:34:00PM +0200, Roger Pau Monné wrote:
> Hello,
>
> The discussion in [1] lead to an agreement of the missing pieces in PVH
> (or HVM without a device-model) in order to progress with it's
> implementation.
>
> One of the missing pieces is a new boot ABI, that replaces
On Wed, 2015-06-10 at 16:59 +0100, Jan Beulich wrote:
> >>> On 10.06.15 at 16:34, wrote:
> > For Intel I'm less sure, I've got microcode-20150121.tgz containing
> > microcode.dat. Is that just to be placed at
> > kernel/x86/microcode/GenuineIntel.bin and done, or is there some
> > processing neede
On Tue, 2015-06-09 at 22:54 -0700, Meng Xu wrote:
> Hi Dario and Dagaen,
>
Hi,
> 2015-06-09 5:53 GMT-07:00 Dario Faggioli :
> > Thanks for doing this. The first question I have is whether you run any
> > test/benchmark that you can show the result of here.
>
> Thank you very much Dario for your
On 09/06/2015 09:03, Shameerali Kolothum Thodi wrote:
Hi Julien/Zoli,
Hi Shameer,
http://xenbits.xen.org/gitweb/?p=people/julieng/xen-unstable.git;a=shortlog;h=refs/heads/for-huawei/gicv2-on-gicv3
I had a run of this staging on our D01 board.
Thank you for testing.
Xen fails to boot with
flight 58318 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58318/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-libvirt-xsm 11 guest-start fail REGR. vs. 57815
test-amd64-i386-libvirt
Hi,
On 09/06/2015 19:48, Julien Grall wrote:
I don't usually use CONFIG_DTB_FILE because my bootloader (u-boot via a
script) is creating the different node for Xen (multiboot, chosen,...).
Although, the CONFIG_DTB_FILE implementation in Xen is very obvious
(only 2 lines which override the regist
On 10/06/15 12:36, Ian Campbell wrote:
> libxenevtchn will provide a stable API and ABI for accessing the
> evtchn device.
>
> The functions are moved into the xenevtchn namespace to make a clean
> break from libxc and avoid ambiguity regarding which interfaces are
> stable.
>
> All in-tree users a
On Wed, Jun 10, 2015 at 2:37 AM, Jan Beulich wrote:
On 10.06.15 at 11:26, wrote:
>> On Wed, 2015-06-10 at 10:15 +0100, Jan Beulich wrote:
>>> >>> On 10.06.15 at 10:56, wrote:
>>> > On Tue, 2015-06-09 at 14:53 +0100, Jan Beulich wrote:
>>> >> From: Konrad Rzeszutek Wilk
>>> >>
>>> >> To hel
On 06/10/2015 12:43 AM, Jan Beulich wrote:
On 10.06.15 at 02:09, wrote:
>> Design
>> ==
>
> Reads all quite reasonable; just one minor remark:
>
>> - Core altp2m functionality
>>
>> A new altp2m type is added to the p2m types (in addition to the previous
>> hostp2m and nestedp2m types)
On 10/06/15 12:36, Ian Campbell wrote:
> libxenevtchn will provide a stable API and ABI for accessing the
> evtchn device.
>
> The functions are moved into the xenevtchn namespace to make a clean
> break from libxc and avoid ambiguity regarding which interfaces are
> stable.
>
> All in-tree users
On 06/10/15 11:59, Jan Beulich wrote:
On 10.06.15 at 16:34, wrote:
>> For Intel I'm less sure, I've got microcode-20150121.tgz containing
>> microcode.dat. Is that just to be placed at
>> kernel/x86/microcode/GenuineIntel.bin and done, or is there some
>> processing needed?
>
> The full bl
Ack-by: Don Dugger
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
-Original Message-
From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-boun...@lists.xen.org]
On Behalf Of Jan Beulich
Sent: Tuesday, June 9, 2015 3:06 AM
To: xen-devel
Cc: Zhang, Ya
On Wed, Jun 10, 2015 at 05:01:27PM +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH RFC 0/6+2+2] Begin to disentangle libxenctrl and
> provide some stable libraries"):
> > [stuff]
>
> Most of this looks good to me.
>
> > As part of this change I've begun to get rid of the osdep interface
On 26/05/15 08:55, Lennart Schulte wrote:
> Hi,
> I use a Xen domU with vanilla Linux 3.19 kernel as a middle node. SG is
> switched off via ethtool. I get random packet drops for about 7% of
> small packets (pings, TCP ACKs/SYNs/little payload).
> From the code in Linux 4.0 it seems that the behav
Ian Campbell writes ("[PATCH RFC 0/6+2+2] Begin to disentangle libxenctrl and
provide some stable libraries"):
> [stuff]
Most of this looks good to me.
> As part of this change I've begun to get rid of the osdep interface
> layer, since it is obsolete and just gets in the way. IIRC there were
>
On 10/06/15 16:38, Roger Pau Monné wrote:
> El 10/06/15 a les 15.18, Andrew Cooper ha escrit:
>>> * cr0: bit 31 (PG) must be cleared. Bit 0 (PE) must be set. Other bits
>>>are all undefined.
>> "unspecified" is perhaps better phrasing. Most will be 0, but ET will
>> be set as it is a read-on
Ian Campbell writes ("[PATCH RFC qemu-trad 1/2] qemu-xen-traditional: Use
xentoollog as a separate library"):
> This has been split out of libxenctrl, so the build needs to be able
> to find the header and the library. QEMU does not use xtl_* itself so
> -rpath-link is sufficient to allow linking
On Wed, Jun 10, 2015 at 02:38:15PM +0100, Ross Lagerwall wrote:
> The current code for allocating memory for PV guests batches the
> hypercalls to allocate memory by allocating 1024*1024 extents of order 0
> at a time. To make this faster, first try allocating single extents of
> order 9 (2 MiB) be
On Wed, 2015-06-10 at 10:52 -0400, Julien Grall wrote:
>
> On 10/06/2015 10:45, Ian Campbell wrote:
> > On Wed, 2015-06-10 at 10:40 -0400, Julien Grall wrote:
> >>> ## Virtual LPI injection
> >>>
> >>> As discussed above the `vgic_vcpu_inject_irq` functionality will need
> >>> to be extended to co
longtao.pang writes ("[OSSTEST Nested PATCH v11 7/7] Add test job for nest test
case"):
> 1. This patch adds creation of the nested test job, when job creation
> procedure is invoked.
> 2. Set nested L1's vif model, nestedhvm feature, set specific disk
> size and memory size for nested test by mak
>>> On 10.06.15 at 16:34, wrote:
> For Intel I'm less sure, I've got microcode-20150121.tgz containing
> microcode.dat. Is that just to be placed at
> kernel/x86/microcode/GenuineIntel.bin and done, or is there some
> processing needed?
The full blob (albeit usually named microcode.bin; microcode
>>> On 10.06.15 at 16:53, wrote:
> El 10/06/15 a les 15.15, Jan Beulich ha escrit:
> On 10.06.15 at 14:34, wrote:
>> For my taste, it's getting too
>> close to something that could be a legitimate 32-bit kernel pointer
>> (agreed, all values could be valid pointers in 32-bit OSes, but with
>>
> -Original Message-
> From: Fabio Fantoni [mailto:fabio.fant...@m2r.biz]
> Sent: 10 June 2015 15:50
> To: Paul Durrant; xen-de...@lists.xenproject.org
> Cc: Andrew Cooper; Keir (Xen.org); Jan Beulich
> Subject: Re: [Xen-devel] [PATCH 00/17] x86/hvm: I/O emulation cleanup and
> fix
>
> Il
Sorry, forgot to reply to one of your chunks.
El 10/06/15 a les 15.15, Jan Beulich ha escrit:
>> * cr0: bit 31 (PG) must be cleared. Bit 0 (PE) must be set. Other bits
>>are all undefined.
>
> I see that grub1 documentation says so, but I doubt this is realistic
> (even less so for cr4 bit
longtao.pang writes ("[OSSTEST Nested PATCH v11 6/7] Compose the main recipe of
nested test job"):
> The ident and guestname are same of 'nestedl1' for L1 guest VM.
This is going in the right direction.
I think arrangements need to be made to capture the logs for
nestedl1.
> +proc need-hosts/te
On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wrote:
> Secondary vm is running in colo mode. So we will do
> the following things again and again:
> 1. suspend both primay vm and secondary vm
> 2. sync the state
> 3. resume both primary vm and secondary vm
> We will send qemu's state each time i
El 10/06/15 a les 15.18, Andrew Cooper ha escrit:
>> * cr0: bit 31 (PG) must be cleared. Bit 0 (PE) must be set. Other bits
>>are all undefined.
>
> "unspecified" is perhaps better phrasing. Most will be 0, but ET will
> be set as it is a read-only bit in all processors Xen will function on
On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wrote:
> From: Wen Congyang
>
> The guest is paused after libxl_domain_create_restore().
> Secondary vm is running in colo mode. So we need to unpause
> the guest. The current API libxl_domain_unpause() is
> not an internal API. Introduce a new API
On 06/10/2015 05:25 PM, David Vrabel wrote:
On 08/06/15 13:06, Juergen Gross wrote:
Support 64 bit pv-domains with more than 512GB of memory.
Tested with 64 bit dom0 on machines with 8GB and 1TB and 32 bit dom0 on a
8GB machine. Conflicts between E820 map and different hypervisor populated
memo
flight 58326 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58326/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 57854
test-amd64-i386-xl-qemut-w
From: Konrad Rzeszutek Wilk
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit a6dfa128ce5c414ab46b1d690f7a1b8decb8526d upstream.
A huge amount of NIC drivers use the DMA API, however if
compiled under 32-bit an very important part of the DMA AP
On 08/06/15 13:06, Juergen Gross wrote:
> Support 64 bit pv-domains with more than 512GB of memory.
>
> Tested with 64 bit dom0 on machines with 8GB and 1TB and 32 bit dom0 on a
> 8GB machine. Conflicts between E820 map and different hypervisor populated
> memory areas have been tested via a fake
On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wrote:
> When we are under COLO, we will send dirty page bitmap info from
> secondary to primary at every checkpoint.
... and this is a _libxl_ operation? Is that the right layer here?
> So we need to get/test
> the dirty page bitmap. We just expo
On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wrote:
> From: Wen Congyang
>
> For PVHVM, the hypercall return code is 0, and it can be resumed
> in a new domain context.
> we suspend PVHVM and resume it is like this:
> 1. suspend it via evtchn
> 2. modifty the return code to 1
> 3. the guest k
The two routines share most of their logic.
Signed-off-by: Boris Ostrovsky
Reviewed-by: Dietmar Hahn
---
xen/arch/x86/hvm/vpmu.c| 75 --
xen/include/asm-x86/hvm/vpmu.h | 14 ++--
2 files changed, 41 insertions(+), 48 deletions(-)
diff --git a
Add support for handling PMU interrupts for PV(H) guests.
VPMU for the interrupted VCPU is unloaded until the guest issues XENPMU_flush
hypercall. This allows the guest to access PMU MSR values that are stored in
VPMU context which is shared between hypervisor and domain, thus avoiding
traps to hy
Save VPMU state during context switch for both HVM and PV(H) guests.
A subsequent patch ("x86/VPMU: NMI-based VPMU support") will make it possible
for vpmu_switch_to() to call vmx_vmcs_try_enter()->vcpu_pause() which needs
is_running to be correctly set/cleared. To prepare for that, call
context_
Code for initializing/tearing down PMU for PV guests
Signed-off-by: Boris Ostrovsky
Acked-by: Daniel De Graaf
Acked-by: Jan Beulich
---
tools/flask/policy/policy/modules/xen/xen.te | 4 +
xen/arch/x86/domain.c| 2 +
xen/arch/x86/hvm/hvm.c | 1
Since PMU is now not HVM specific we can move VPMU-related files up from
arch/x86/hvm/ directory.
Specifically:
arch/x86/hvm/vpmu.c -> arch/x86/cpu/vpmu.c
arch/x86/hvm/svm/vpmu.c -> arch/x86/cpu/vpmu_amd.c
arch/x86/hvm/vmx/vpmu_core2.c -> arch/x86/cpu/vpmu_intel.c
include/asm-x86/h
1 - 100 of 219 matches
Mail list logo
