>>> On 08.07.15 at 18:43, wrote:
> On 08/07/2015 16:57, Paul Durrant wrote:
>>> -Original Message-
>>> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
>>> boun...@lists.xen.org] On Behalf Of Jan Beulich
>>> Sent: 08 July 2015 16:53
>>> To: Andrew Cooper; Paul Durrant
>>> Cc: xen-d
flight 59255 rumpuserxen real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59255/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 5 rumpuserxen-build fail REGR. vs. 33866
build-i386-rumpuserxe
On 07/09/2015 01:52 AM, Tamas K Lengyel wrote:
> A couple spots in x86/monitor used hvm_funcs directly. This patch adds an
> extra
> wrapper for enable_msr_exit_interception and changes monitor.c to use only the
> wrappers.
>
> Signed-off-by: Tamas K Lengyel
> ---
> xen/arch/x86/monitor.c
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Saturday, June 20, 2015 2:45 AM
>
> The two routines share most of their logic.
>
> Signed-off-by: Boris Ostrovsky
> Reviewed-by: Dietmar Hahn
Reviewed-by: Kevin Tian
> ---
> xen/arch/x86/hvm/vpmu.c| 75
> ++
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Saturday, June 20, 2015 2:45 AM
>
> Add support for privileged PMU mode (XENPMU_MODE_ALL) which allows privileged
> domain (dom0) profile both itself (and the hypervisor) and the guests. While
> this mode is on profiling in guests
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Saturday, June 20, 2015 2:45 AM
>
> Move some VPMU initilization operations into __initcalls to avoid performing
> same tests and calculations for each vcpu.
>
> Signed-off-by: Boris Ostrovsky
> Acked-by: Jan Beulich
Acked-by:
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.
CC: Ian Jackson
CC: Stefano Stabelli
Previously we always fix that predefined boundary as 2G to handle
conflict between memory and rdm, but now this predefined boundar
can be changes with the parameter "rdm_mem_boundary" in .cfg file.
CC: Ian Jackson
CC: Stefano Stabellini
CC: Ian Campbell
CC: Wei Liu
Acked-by: Wei Liu
Signed-of
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.
CC: Ya
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
This patch passes rdm reservation policy to xc_assign_device() so the policy
is checked when assigning devices to a VM.
Note this also bring some fallout to python usage of xc_assign_device().
CC: Ian Jackson
CC: Stefano Stabellini
CC: Ian Campbell
CC: Wei Liu
CC: David Scott
Acked-by: Wei L
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.
CC: Jan Beulich
CC: Yang Zhang
CC: Kevin Tian
Signed-off-by: Jan Beulich
Signed-off-by: Tiejun Chen
Acked-by: Kevin Tian
---
v
USB RMRR may conflict with guest BIOS region. In such case, identity
mapping setup is simply skipped in previous implementation. Now we
can handle this scenario cleanly with new policy mechanism so previous
hack code can be removed now.
CC: Yang Zhang
CC: Kevin Tian
Signed-off-by: Tiejun Chen
A
This patch enables XENMEM_memory_map in hvm. So hvmloader can
use it to setup the e820 mappings.
CC: Keir Fraser
CC: Jan Beulich
CC: Andrew Cooper
Signed-off-by: Tiejun Chen
Reviewed-by: Tim Deegan
Reviewed-by: Kevin Tian
Acked-by: Jan Beulich
Acked-by: George Dunlap
---
v5 ~ v7:
* Nothin
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 RDM.
RMRR can reside in address space beyond 4
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
When allocating mmio address for PCI bars, we need to make
sure they don't overlap with reserved regions.
CC: Keir Fraser
CC: Jan Beulich
CC: Andrew Cooper
CC: Ian Jackson
CC: Stefano Stabellini
CC: Ian Campbell
CC: Wei Liu
Signed-off-by: Tiejun Chen
---
v6 ~ v7:
* Nothing is changed.
v5
Now we can use that memory map to build our final
e820 table but it may need to reorder all e820
entries.
CC: Keir Fraser
CC: Jan Beulich
CC: Andrew Cooper
CC: Ian Jackson
CC: Stefano Stabellini
CC: Ian Campbell
CC: Wei Liu
Signed-off-by: Tiejun Chen
---
v5 ~ v7:
* Nothing is changed.
v4
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
This patch introduces user configurable parameters to specify RDM
resource and according policies,
Global RDM parameter:
rdm = "strategy=host,policy=strict/relaxed"
Per-device RDM parameter:
pci = [ 'sbdf, rdm_policy=strict/relaxed' ]
Global RDM parameter, "strategy", allows user to speci
v7:
* Need to rename some parameters:
In the xl rdm config parsing, `reserve=' should be `policy='.
In the xl pci config parsing, `rdm_reserve=' should be `rdm_policy='.
The type `libxl_rdm_reserve_flag' should be `libxl_rdm_policy'.
The field name `reserve' in `libxl_rdm_reserve' should b
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.
Note this guest e820 table would be same as before if the
platform has no any RDM or we disable RDM (by default).
CC: Ian
This patch parses to enable user configurable parameters to specify
RDM resource and according policies,
Global RDM parameter:
rdm = "strategy=host,policy=strict/relaxed"
Per-device RDM parameter:
pci = [ 'sbdf, rdm_policy=strict/relaxed' ]
Default per-device RDM policy is same as default
2015-07-08 1:01 GMT-07:00 Dario Faggioli :
> [Trimming the Cc-list a bit, to avoid bothering Wei and Jan]
>
> On Tue, 2015-07-07 at 22:56 -0700, Meng Xu wrote:
>> Hi Dario,
>>
> Hi,
>
>> 2015-07-07 7:03 GMT-07:00 Dario Faggioli :
>> >
>> > On Mon, 2015-07-06 at 22:51 -0700, Meng Xu wrote:
>
>> > So
> -Original Message-
> From: Dario Faggioli [mailto:dario.faggi...@citrix.com]
> Sent: Thursday, July 02, 2015 4:21 PM
> To: Wu, Feng
> Cc: xen-devel; k...@xen.org; jbeul...@suse.com; andrew.coop...@citrix.com;
> Tian, Kevin; Zhang, Yang Z; george.dun...@eu.citrix.com
> Subject: Re: Fwd:
On Wed, Jul 08, 2015 at 05:32:11PM +0100, Jan Beulich wrote:
> >>> On 08.07.15 at 18:17, wrote:
> > I think it has to do with the fact that I've got CPU #0 on socket #1,
> > while Boris' (and perhaps Chao's too) test box have it on socket #0.
>
> Ah, yes, this is indeed a case I didn't consider w
From: "Luis R. Rodriguez"
This lets drivers take advantage of PAT when available. It should help
with the transition of converting video drivers over to ioremap_wc()
to help with the goal of eventually using _PAGE_CACHE_UC over
_PAGE_CACHE_UC_MINUS on x86 on ioremap_nocache(), see:
de33c442ed2
From: "Luis R. Rodriguez"
This driver uses the same area for MTRR as for the ioremap().
Convert the driver from using the x86-specific MTRR code to the
architecture-agnostic arch_phys_wc_add(). It will avoid MTRRs if
write-combining is available. In order to take advantage of that
also ensure th
From: "Luis R. Rodriguez"
Convert the driver from using the x86-specific MTRR code to the
architecture-agnostic arch_phys_wc_add(). It will avoid MTRRs if
write-combining is available. In order to take advantage of that also
ensure the ioremapped area is requested as write-combining.
There are a
From: "Luis R. Rodriguez"
PCI BARs tell us whether prefetching is safe, but they don't say
anything about write combining (WC). WC changes ordering rules and
allows writes to be collapsed, so it's not safe in general to use it on
a prefetchable region.
Add pci_iomap_wc() and pci_iomap_wc_range()
From: "Luis R. Rodriguez"
This driver uses the same area for MTRR as for the ioremap().
Convert the driver from using the x86-specific MTRR code to the
architecture-agnostic arch_phys_wc_add(). It will avoid MTRRs if
write-combining is available. In order to take advantage of that
also ensure th
From: "Luis R. Rodriguez"
The driver doesn't use mtrr_add() or arch_phys_wc_add() but since we
know the framebuffer is isolated already on an ioremap() we can take
advantage of write combining for performance where possible.
In this case there are a few motivations for this:
a) Take advantage o
From: "Luis R. Rodriguez"
Convert the driver from using the x86-specific MTRR code to the
architecture-agnostic arch_phys_wc_add(). It will avoid MTRR if
write-combining is available, in order to take advantage of that
also ensure the ioremapped area is requested as write-combining.
There are a
From: "Luis R. Rodriguez"
Convert the driver from using the x86-specific MTRR code to the
architecture-agnostic arch_phys_wc_add(). It will avoid MTRR if
write-combining is available, in order to take advantage of that also
ensure the ioremapped area is requested as write-combining.
There are a
From: "Luis R. Rodriguez"
Ingo,
Boris is on vacation, he picked up these patches on his bp#tip-mm tree [0]
and they have baked there for a while now. That tree receives 0-day
bot testing, but other than that its not clear what other tests were
run on these patches. Boris modified the commit logs
From: Elena Ufimtseva
v9 of rmrr command line patches.
Add Xen command line option rmrr to specify RMRR
regions for devices that are not defined in ACPI thus
causing IO Page Fault while booting dom0 in PVH mode.
These additional regions will be added to the list of
RMRR regions parsed from ACPI.
From: Elena Ufimtseva
In preparation for patch "iommu: add rmrr Xen command line option for
extra rmrrs" which will use it.
Signed-off-by: Elena Ufimtseva
---
xen/include/xen/pci.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen/include/xen/pci.h b/xen/include/xen/pci.h
index 3908146
On Wed, Jul 08, 2015 at 04:38:52PM +0100, Jan Beulich wrote:
> >>> On 08.07.15 at 17:11, wrote:
> > On Wed, 2015-07-08 at 13:38 +0100, Jan Beulich wrote:
> >> >>> On 08.07.15 at 11:36, wrote:
> >> > @@ -84,11 +85,21 @@ void *stack_base[NR_CPUS];
> >> > static void smp_store_cpu_info(int id)
> >>
From: Elena Ufimtseva
On some platforms RMRR regions may be not specified
in ACPI and thus will not be mapped 1:1 in dom0. This
causes IO Page Faults and prevents dom0 from booting
in PVH mode.
New Xen command line option rmrr allows to specify
such devices and memory regions. These regions are a
From: Elena Ufimtseva
For sbdf's parsing in RMRR command line add __parse_pci with additional
parameter def_seg. __parse_pci will help to identify if segment was
found in string being parsed or default segment was used.
Make a wrapper parse_pci so the rest of the callers are not affected.
Signed
From: Elena Ufimtseva
In preparation for auxiliary RMRR data provided on Xen
command line, make RMRR adding a separate function.
Also free memery for rmrr device scope in error path.
Signed-off-by: Elena Ufimtseva
---
xen/drivers/passthrough/vtd/dmar.c | 126 +++---
On Wed, Jul 08, 2015 at 11:02:10AM +0100, Wei Liu wrote:
>
> Chao, 4.6 freeze is on Friday. Can you fix that minor bug and
> repost your series within two days?
>
Sure, I will post another version later today.
Thanks,
Chao
___
Xen-devel mailing list
X
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Saturday, June 20, 2015 2:45 AM
>
> Add runtime interface for setting PMU mode and flags. Three main modes are
> provided:
> * XENPMU_MODE_OFF: PMU is not virtualized
> * XENPMU_MODE_SELF: Guests can access PMU MSRs and receive P
2015-07-08 1:33 GMT-07:00 Dario Faggioli :
> On Tue, 2015-07-07 at 23:06 -0700, Meng Xu wrote:
>> 2015-07-07 7:39 GMT-07:00 Dario Faggioli :
>> > On Tue, 2015-07-07 at 09:59 +0100, Jan Beulich wrote:
>> >> >>> On 29.06.15 at 04:44, wrote:
>> >> > --- a/xen/common/Makefile
>> >> > +++ b/xen/common/
Add an option to the vm_event response to toggle singlestepping on the vCPU.
This is only supported on Intel CPUs which have Monitor Trap Flag capability.
Singed-off-by: Tamas K Lengyel
Acked-by: Razvan Cojocaru
---
v4: Use new inline wrapper for hvm_func
Fix comment still referring to mem_e
A couple spots in x86/monitor used hvm_funcs directly. This patch adds an extra
wrapper for enable_msr_exit_interception and changes monitor.c to use only the
wrappers.
Signed-off-by: Tamas K Lengyel
---
xen/arch/x86/monitor.c| 7 ++-
xen/include/asm-x86/hvm/hvm.h | 11 +++
Add option to monitor_op domctl to determine the monitor capabilities of the
system.
Signed-off-by: Tamas K Lengyel
---
v4: add inline function wrapper for is_singlestep_supported to hvm.h
v3: move is_singlestep_supported into vmx
sanity check capabilities for each monitor_op enable/disable
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Wednesday, July 08, 2015 9:09 PM
>
> On 08/07/2015 13:46, Jan Beulich wrote:
> On 08.07.15 at 13:00, wrote:
> >>> @@ -1848,6 +1869,33 @@ static struct hvm_function_table __initdata
> >>> vmx_function_table = {
> >>> .enabl
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, July 08, 2015 8:46 PM
>
> >>> On 08.07.15 at 13:00, wrote:
> >> @@ -1848,6 +1869,33 @@ static struct hvm_function_table __initdata
> >> vmx_function_table = {
> >> .enable_msr_exit_interception = vmx_enable_msr_exit_intercepti
flight 59186 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59186/
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. 590
On 07/08/2015 06:04 AM, Michal Privoznik wrote:
On 07.07.2015 01:27, Jim Fehlig wrote:
On 07/06/2015 03:46 PM, Jim Fehlig wrote:
In Xen, dom0 is really just another domain that supports ballooning,
adding/removing devices, changing vcpu configuration, etc. This patch
adds support to the libxl d
From: Liang Li
Date: Mon, 6 Jul 2015 08:42:56 +0800
> There are two duplicated xenvif_zerocopy_callback() definitions.
> Remove one of them.
>
> Signed-off-by: Liang Li
Applied, thanks.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://list
On 07/08/2015 10:50 AM, Jan Beulich wrote:
On 08.07.15 at 16:40, wrote:
On 07/08/2015 10:08 AM, Jan Beulich wrote:
On 08.07.15 at 15:59, wrote:
On 07/08/2015 02:48 AM, Jan Beulich wrote:
On 07.07.15 at 19:13, wrote:
On 07/07/2015 12:15 PM, Jan Beulich wrote:
On 07.07.15 at 17:46, wrote:
flight 59185 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59185/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-xsm 11 guest-start fail REGR. vs. 58842
Regressions which are reg
flight 59177 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59177/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 58581
Tests which are failin
flight 59179 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59179/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 59121
test-amd64-i386-xl-qemuu-win7-amd64 1
Instead we have the emulation registers ->init functions which
consult the host values to see what the initial value should be
and they are responsible for populating the dev.config.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions
Hey,
This is a follow up patch - as we have now removed the XenPTReg->data and
are using dev.config for registers, and each ->init routine sets the
proper registers (and reads from the host SysFS) - there is no need
to slurp up at the start all of the configuration registers - as we
end up overwri
Hi Wei,
Given where we stand (close) on the altp2m patch series - we would like to
request an extension of about a week to complete the last couple of patches in
the series for inclusion in 4.6.
Some of the suggestions may have implications on other patches and on our tests
hence asking for th
On 07/08/2015 12:17 PM, Dario Faggioli wrote:
On Wed, 2015-07-08 at 16:38 +0100, Jan Beulich wrote:
On 08.07.15 at 17:11, wrote:
On Wed, 2015-07-08 at 13:38 +0100, Jan Beulich wrote:
On 08.07.15 at 11:36, wrote:
@@ -84,11 +85,21 @@ void *stack_base[NR_CPUS];
static void smp_store_cpu_info
. snip..
> diff --git a/xen/drivers/passthrough/vtd/dmar.c
> b/xen/drivers/passthrough/vtd/dmar.c
> index a8e1e5d..fa659a9 100644
> --- a/xen/drivers/passthrough/vtd/dmar.c
> +++ b/xen/drivers/passthrough/vtd/dmar.c
> @@ -42,6 +42,8 @@
> #define MIN_SCOPE_LEN (sizeof(struct acpi_dmar_device_scope
On Tue, Jun 30, 2015 at 07:34:01PM -0400, elena.ufimts...@oracle.com wrote:
> From: Elena Ufimtseva
>
> For sbdf'si parsing in rmrr command line add __parse_pci with addtional
sbdf'si ?
s/rmrr/RMRR/
s/addtional/additional/
> parameter def_seg. __parse_pci will help to identify if segment was
On Tue, Jun 30, 2015 at 07:34:00PM -0400, elena.ufimts...@oracle.com wrote:
> From: Elena Ufimtseva
>
> In preparation for auxiliary RMRR data provided on Xen
> command line, make RMRR adding a separate function.
> Also free memery for rmrr device scope in error path.
> I will also post additiona
On Tue, Jun 30, 2015 at 07:33:59PM -0400, elena.ufimts...@oracle.com wrote:
> From: Elena Ufimtseva
>
You usually say why you need this patch. Something as simple as:
"In preperation for patch which will use it" is OK.
> Signed-off-by: Elena Ufimtseva
> ---
> xen/include/xen/pci.h | 2 +
flight 59169 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59169/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64 11 guest-saverestore fail REGR. vs.
59059
test-amd64-am
On Wed, Jul 8, 2015 at 10:39 AM, Jan Beulich wrote:
> >>> On 07.07.15 at 15:52, wrote:
> > --- a/xen/arch/x86/hvm/hvm.c
> > +++ b/xen/arch/x86/hvm/hvm.c
> > @@ -6431,6 +6431,17 @@ int hvm_debug_op(struct vcpu *v, int32_t op)
> > return rc;
> > }
> >
> > +void hvm_toggle_singlestep(struct v
On Wed, Jul 8, 2015 at 10:37 AM, Jan Beulich wrote:
> >>> On 07.07.15 at 15:52, wrote:
> > --- a/xen/arch/x86/monitor.c
> > +++ b/xen/arch/x86/monitor.c
> > @@ -42,10 +42,29 @@ int status_check(struct xen_domctl_monitor_op *mop,
> bool_t status)
> > return 0;
> > }
> >
> > +static inline u
On 08/07/2015 16:57, Paul Durrant wrote:
>> -Original Message-
>> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
>> boun...@lists.xen.org] On Behalf Of Jan Beulich
>> Sent: 08 July 2015 16:53
>> To: Andrew Cooper; Paul Durrant
>> Cc: xen-de...@lists.xenproject.org; Keir (Xen.org)
On Wed, 2015-07-08 at 17:01 +0100, George Dunlap wrote:
> On Fri, Jul 3, 2015 at 4:49 PM, Dario Faggioli
> > --- a/xen/common/schedule.c
> > +++ b/xen/common/schedule.c
> > @@ -455,8 +455,8 @@ void vcpu_unblock(struct vcpu *v)
> > * Do the actual movemet of a vcpu from old to new CPU. Locks for
>>> On 08.07.15 at 18:17, wrote:
> I think it has to do with the fact that I've got CPU #0 on socket #1,
> while Boris' (and perhaps Chao's too) test box have it on socket #0.
Ah, yes, this is indeed a case I didn't consider when validating
Chao's analysis.
Jan
>>> On 03.07.15 at 18:25, wrote:
> --- a/xen/arch/x86/hvm/intercept.c
> +++ b/xen/arch/x86/hvm/intercept.c
> @@ -125,10 +125,7 @@ int hvm_process_io_intercept(const struct hvm_io_handler
> *handler,
> {
> struct vcpu *curr = current;
> struct hvm_vcpu_io *vio = &curr->arch.hvm_vcpu.hvm
>>> On 03.07.15 at 18:25, wrote:
> -void relocate_io_handler(
> -struct domain *d, unsigned long old_addr, unsigned long new_addr,
> -unsigned int size, int type)
> +void relocate_portio_handler(struct domain *d, uint16_t old_port,
> + uint16_t new_port, unsigne
> On 8 Jul 2015, at 15:46, Chen, Tiejun wrote:
>
> On 2015/7/8 21:27, Ian Jackson wrote:
>> Chen, Tiejun writes ("Re: [v6][PATCH 10/16] tools: introduce some new
>> parameters to set rdm policy"):
>>> On 2015/7/8 19:47, Ian Jackson wrote:
I appreciate that I have come to this review late.
On Fri, Jul 3, 2015 at 4:49 PM, Dario Faggioli
wrote:
> And this time, do it right. In fact, a similar change was
> attempted in 93be8285a79c6 ("cpupools: update domU's node-affinity
> on the cpupool_unassign_cpu() path"). But that was buggy, and got
> reverted with 8395b67ab0b8a86.
>
> However, e
On Wed, 2015-07-08 at 16:38 +0100, Jan Beulich wrote:
> >>> On 08.07.15 at 17:11, wrote:
> > On Wed, 2015-07-08 at 13:38 +0100, Jan Beulich wrote:
> >> >>> On 08.07.15 at 11:36, wrote:
> >> > @@ -84,11 +85,21 @@ void *stack_base[NR_CPUS];
> >> > static void smp_store_cpu_info(int id)
> >> > {
>
>>> On 08.07.15 at 17:57, wrote:
>> -Original Message-
>> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
>> boun...@lists.xen.org] On Behalf Of Jan Beulich
>> Sent: 08 July 2015 16:53
>> To: Andrew Cooper; Paul Durrant
>> Cc: xen-de...@lists.xenproject.org; Keir (Xen.org)
>> Sub
>>> On 03.07.15 at 18:25, wrote:
> -int stdvga_intercept_mmio(ioreq_t *p)
> +static bool_t stdvga_mem_accept(const struct hvm_io_handler *handler,
> +const ioreq_t *p)
> {
> -struct domain *d = current->domain;
> -struct hvm_hw_stdvga *s = &d->arch.hvm_doma
>>> On 03.07.15 at 18:25, wrote:
> @@ -1465,11 +1462,12 @@ int hvm_domain_initialise(struct domain *d)
> goto fail0;
>
> d->arch.hvm_domain.params = xzalloc_array(uint64_t, HVM_NR_PARAMS);
> -d->arch.hvm_domain.io_handler = xmalloc(struct hvm_io_handler);
> +d->arch.hvm_dom
Commit 902d1b5c310fb63b511f0b967cf5f32d3f605f3d (x86,arm: remove
asm/spinlock.h from all architectures) inadvertantly removed an
x86-specific optimization for read_unlock*().
Re-add asm/spinlock.h to allow architectures to provide an optmized
_raw_read_unlock() and make x86 provide the previous im
On Fri, Jul 3, 2015 at 4:49 PM, Dario Faggioli
wrote:
> The function is called both when we want to remove a cpu
> from a cpupool, and during cpu teardown, for suspend or
> shutdown. If, however, the boot cpu (cpu 0, most of the
> times) is not present in the default cpupool, during
> suspend or s
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 08 July 2015 16:57
> To: Paul Durrant
> Cc: xen-de...@lists.xenproject.org; Keir (Xen.org)
> Subject: Re: [PATCH v6 04/16] x86/hvm: restrict port numbers to uint16_t
> and sizes to unsigned int
>
> >>> On 03.07.15
>>> On 03.07.15 at 18:25, wrote:
> Building on the previous patch, this patch restricts portio port numbers
> to uint16_t in registration/relocate calls and portio_action_t. It also
> changes portio sizes to unsigned int which then allows the io_handler
> size field to reduce to an unsigned int.
> -Original Message-
> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
> boun...@lists.xen.org] On Behalf Of Jan Beulich
> Sent: 08 July 2015 16:53
> To: Andrew Cooper; Paul Durrant
> Cc: xen-de...@lists.xenproject.org; Keir (Xen.org)
> Subject: Re: [Xen-devel] [PATCH v6 02/16] x86
>>> On 03.07.15 at 18:25, wrote:
> +static int hvmemul_linear_mmio_access(
> +unsigned long gla, unsigned int size, uint8_t dir, uint8_t *buffer,
> +uint32_t pfec, struct hvm_emulate_ctxt *hvmemul_ctxt, bool_t known_gpfn)
> +{
> +struct hvm_vcpu_io *vio = ¤t->arch.hvm_vcpu.hvm_io;
> +
On Wed, 2015-07-08 at 16:25 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH OSSTEST v8 05/14] distros: Support pvgrub
> for Wheezy too."):
> > On Wed, 2015-07-08 at 14:58 +0100, Ian Jackson wrote:
> > > Acked-by: Ian Jackson
> >
> > Thanks. I think that makes all but the last patch
On 8 July 2015 at 15:06, Michael S. Tsirkin wrote:
> On Tue, Jul 07, 2015 at 02:32:38PM +0100, Paul Durrant wrote:
>> There is a mismatch between the definition of ioservid_t in
>> xen_common.h and the definition in the Xen publix headers. This patch
>> corrects the definition in xen_common.h.
>>
On Wed, 2015-07-08 at 16:21 +0100, Ian Jackson wrote:
> Provide an appropriate --html-dir option to sg-report-flight.
> (Bisection flights still do not run sg-report-host-history and
> sg-report-job-history, which are fairly expensive.)
>
> Make references to jobs from sg-report-job-history and
>
Ian Campbell writes ("[PATCH OSSTEST v6] mg-all-branch-statuses: Show how up to
date each branch is"):
> Using report_find_push_age_info allows us to provide counts of
> attempts since the last baseline on current tip as well as the first
> attempt of each of those.
...
> v6: - Propagate cron outp
On Wed, 2015-07-08 at 16:21 +0100, Ian Jackson wrote:
> When this assertion fails, dump the troublesome harness revision and
> requested host flags, too.
>
> Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lis
Ian Campbell writes ("Re: [OSSTEST PATCH 1/4] Email reports: Sort out
recipients and Reply-to"):
> On Wed, 2015-07-08 at 16:21 +0100, Ian Jackson wrote:
> > Deployment notes:
> >
> > Keir and Stefano will no longer receive automatic CCs of certain
> > reports, and should subscribe to the osstest-
On 07/08/2015 11:38 AM, Jan Beulich wrote:
On 08.07.15 at 17:11, wrote:
On Wed, 2015-07-08 at 13:38 +0100, Jan Beulich wrote:
On 08.07.15 at 11:36, wrote:
@@ -84,11 +85,21 @@ void *stack_base[NR_CPUS];
static void smp_store_cpu_info(int id)
{
struct cpuinfo_x86 *c = cpu_data + id;
On Wed, 2015-07-08 at 16:21 +0100, Ian Jackson wrote:
> Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
(I think you cleared up the existing mess already)
> ---
> mg-branch-setup |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mg-branch-setup b/mg-branch-set
>>> On 03.07.15 at 18:25, wrote:
> Changelog (now per-patch)
> -
That's quite nice, but still not really helpful when not put in the
individual patches - one still needs to keep this one and the patch
open to follow things incrementally.
Jan
>>> On 08.07.15 at 17:11, wrote:
> On Wed, 2015-07-08 at 13:38 +0100, Jan Beulich wrote:
>> >>> On 08.07.15 at 11:36, wrote:
>> > @@ -84,11 +85,21 @@ void *stack_base[NR_CPUS];
>> > static void smp_store_cpu_info(int id)
>> > {
>> > struct cpuinfo_x86 *c = cpu_data + id;
>> > +unsigned
On 6/19/2015 1:44 PM, Boris Ostrovsky wrote:
A number of fields of PMU control MSRs are defined as Reserved. AMD
documentation requires that such fields are preserved when the register
is written by software.
Add checks to amd_vpmu_do_wrmsr() to make sure that guests don't attempt
to modify thos
When this assertion fails, dump the troublesome harness revision and
requested host flags, too.
Signed-off-by: Ian Jackson
---
Osstest/JobDB/Executive.pm |9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/Osstest/JobDB/Executive.pm b/Osstest/JobDB/Executive.pm
index
On Wed, 2015-07-08 at 16:21 +0100, Ian Jackson wrote:
> No longer send reports, or copies, to named individuals. Instead,
> send all output to 1. appropriate development mailing lists 2. the new
> osstest-admin@xenproject administrator alias, and 3. Bcc the new
> osstest-output list.
>
> Bisectio
Ian Campbell writes ("Re: [PATCH OSSTEST v8 05/14] distros: Support pvgrub for
Wheezy too."):
> On Wed, 2015-07-08 at 14:58 +0100, Ian Jackson wrote:
> > Acked-by: Ian Jackson
>
> Thanks. I think that makes all but the last patch acked.
You mean
"make-distros-flight: Use ftp.debian.org direct
On Wed, 2015-07-08 at 16:23 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST v1] ap-fetch-version: Arrange for
> osstest merges from upstream to be stable"):
> > If a downstream osstest instance has nothing to test it its local
> > pretest then it will attempt to merge from the ups
Provide an appropriate --html-dir option to sg-report-flight.
(Bisection flights still do not run sg-report-host-history and
sg-report-job-history, which are fairly expensive.)
Make references to jobs from sg-report-job-history and
sg-report-host-history go to the /info.html page, not the webserve
1 - 100 of 279 matches
Mail list logo