The default max-segments of indirect requests was 32, so IO operations with
bigger block size(>32*4k) would be split and make performance drop.
Nowadays backend device usually support 512k max_sectors_kb on desktop,
and usually larger on server machines connected with high-end storage system.
The
Instead of manually list each hypercall in arch/x86/xen/xen-head.S
use the auto generated symbol list.
This also corrects the wrong address of xen_hypercall_mca which was
located 32 bytes higher than it should.
Symbol addresses have been verified to match the correct ones via
objdump output.
Bas
Today there are several places in the kernel which build tables
containing one entry for each possible Xen hypercall. Create an
infrastructure to be able to generate these tables at build time.
Based-on-patch-by: Jan Beulich
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/s
Instead of manually list all hypervisor calls in arch/x86/xen/trace.c
use the auto generated list.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/xen/trace.c | 50 --
1 file changed, 4 insertions(+), 46 deletions(-)
diff --gi
The Xen hypercalls are defined in include/xen/interface/xen.h. There
are some places where for each hypercall a table element is created.
Instead of manually add each hypercall element to these tables use
an auto generated header built during the make process of the kernel.
Changes in V2:
- add "a
The header include/xen/interface/xen.h doesn't contain all definitions
from Xen's version of that header. Update it accordingly.
Signed-off-by: Juergen Gross
Reviewed-by: David Vrabel
---
arch/x86/xen/trace.c| 2 +-
include/xen/interface/xen.h | 6 +-
2 files changed, 6 insertions(+
CCed Stefano.
Thanks
Tiejun
On 2015/1/21 15:19, Tiejun Chen wrote:
When we're working to support IGD GFX passthrough with qemu
upstream, instead of "-gfx_passthru" we'd like to make that
a machine option, "-machine xxx,gfx_passthru=on". This need
to bring several changes on tool side.
Signed-o
When we're working to support IGD GFX passthrough with qemu
upstream, instead of "-gfx_passthru" we'd like to make that
a machine option, "-machine xxx,gfx_passthru=on". This need
to bring several changes on tool side.
Signed-off-by: Tiejun Chen
---
tools/libxl/libxl_dm.c | 19 +-
branch xen-unstable
xen branch xen-unstable
job test-amd64-amd64-xl-pvh-intel
test xen-boot
Tree: linux
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unst
Eric Blake wrote:
> On 01/20/2015 09:09 PM, Jim Fehlig wrote:
>
>> When libvirt is configured --without-xen, building the xlconfigtest
>> fails with
>>
>> CCLD xlconfigtest
>> /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/crt1.o
>> In function `_start': (.text+0x20): undefi
Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST v2 18/18] WIP: libvirt: migration +
> save/restore support."):
>
>> Note that this remains stubbed out, since making it actually work
>> requires more work (i.e. I need to figure out what is involved, seem
>> to need TLS and a CA etc...)
Ian Campbell wrote:
> On Mon, 2015-01-19 at 09:37 +, Ian Campbell wrote:
>
>> On Mon, 2015-01-19 at 04:48 +, xen.org wrote:
>>
>>> branch xen-unstable
>>> xen branch xen-unstable
>>> job build-armhf-libvirt
>>> test libvirt-build
>>>
>>> Tree: libvirt git://libvirt.org/libvirt.git
>
flight 33575 xen-4.4-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33575/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 13 guest-localmigrate/x10 fail REGR. vs.
33563
Regressions
On 01/20/2015 09:09 PM, Jim Fehlig wrote:
> When libvirt is configured --without-xen, building the xlconfigtest
> fails with
>
> CCLD xlconfigtest
> /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/crt1.o
> In function `_start': (.text+0x20): undefined reference to `main'
> co
When libvirt is configured --without-xen, building the xlconfigtest
fails with
CCLD xlconfigtest
/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/crt1.o
In function `_start': (.text+0x20): undefined reference to `main'
collect2: error: ld returned 1 exit status
Introduced in
> From: George Dunlap
> Sent: Tuesday, January 20, 2015 8:57 PM
>
> On Tue, Jan 20, 2015 at 12:52 AM, Tian, Kevin wrote:
> >> For RMRRs in the BIOS area, libxl will already need to know where that
> >> area is (to know that it doesn't need to fit it into the MMIO hole); if
> >> we just make it sm
Now we could pass PCI domain combined with bus number
in u32 argu. Because in arm/arm64, PCI domain number
is assigned by pci_bus_assign_domain_nr(). So we leave
pci_scan_root_bus() and pci_create_root_bus() in arm/arm64
unchanged. A new function pci_host_assign_domain_nr()
will be introduced for a
flight 33574 xen-4.3-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33574/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-intel 7 redhat-installfail REGR. vs. 33427
test-amd64-amd64-
From: Arnd Bergmann
Use pci_scan_root_bus() instead of deprecated function
pci_scan_bus_parented().
Signed-off-by: Arnd Bergmann
Signed-off-by: Yijing Wang
CC: Konrad Rzeszutek Wilk
CC: xen-de...@lists.xenproject.org
---
drivers/pci/xen-pcifront.c | 10 +++---
1 files changed, 7 insert
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Tuesday, January 20, 2015 6:49 PM
>
> >>> On 20.01.15 at 11:38, wrote:
> > On Tue, 2015-01-20 at 09:10 +, Jan Beulich wrote:
> >> >>> On 20.01.15 at 09:59, wrote:
> >> >> From: Jan Beulich [mailto:jbeul...@suse.com]
> >> >> Sent: Tuesda
> -Original Message-
> From: Daniel De Graaf [mailto:dgde...@tycho.nsa.gov]
> Sent: Wednesday, January 21, 2015 6:28 AM
> To: Xu, Quan; xen-devel@lists.xen.org
> Cc: ian.campb...@citrix.com; ian.jack...@eu.citrix.com; jbeul...@suse.com;
> k...@xen.org; t...@xen.org; stefano.stabell...@eu.
flight 33576 xen-4.5-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33576/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl 5 xen-boot fail REGR. vs. 33414
Tests which did n
On 01/15/2015 04:21 AM, Quan Xu wrote:
This series of patch enable the virtual Trusted Platform Module (vTPM)
subsystem for Xen on TPM 2.0.
Noted, functionality for a virtual guest operating system (a DomU) is still
TPM 1.2. The main modifcation is on vtpmmgr-stubdom. The challenge is that
TPM 2
flight 33578 qemu-mainline real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/33578/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 5 xen-build fail REGR. vs. 33480
Tests which did not
This patch adds the necessary KVM specific code to allow KVM to
support the CPU halting and kicking operations needed by the queue
spinlock PV code.
Two KVM guests of 20 CPU cores (2 nodes) were created for performance
testing in one of the following three configurations:
1) Only 1 VM is active
This patch adds the necessary XEN specific code to allow XEN to
support the CPU halting and kicking operations needed by the queue
spinlock PV code.
Signed-off-by: Waiman Long
---
arch/x86/xen/spinlock.c | 149 +--
kernel/Kconfig.locks|2 +-
2
This patch adds para-virtualization support to the queue spinlock
code base with minimal impact to the native case. There are some
minor code changes in the generic qspinlock.c file which should be
usable in other architectures. The other code changes are specific
to x86 processors and so are all p
From: Peter Zijlstra
When we allow for a max NR_CPUS < 2^14 we can optimize the pending
wait-acquire and the xchg_tail() operations.
By growing the pending bit to a byte, we reduce the tail to 16bit.
This means we can use xchg16 for the tail part and do away with all
the repeated compxchg() oper
This patch makes the necessary changes at the x86 architecture
specific layer to enable the use of queue spinlock for x86-64. As
x86-32 machines are typically not multi-socket. The benefit of queue
spinlock may not be apparent. So queue spinlock is not enabled.
Currently, there is some incompatibi
This is a preparatory patch that extracts out the following 2 code
snippets to prepare for the next performance optimization patch.
1) the logic for the exchange of new and previous tail code words
into a new xchg_tail() function.
2) the logic for clearing the pending bit and setting the loc
This patch renames the paravirt_ticketlocks_enabled static key to a
more generic paravirt_spinlocks_enabled name.
Signed-off-by: Waiman Long
Signed-off-by: Peter Zijlstra
---
arch/x86/include/asm/spinlock.h |4 ++--
arch/x86/kernel/kvm.c|2 +-
arch/x86/kernel/paravi
Currently, atomic_cmpxchg() is used to get the lock. However, this
is not really necessary if there is more than one task in the queue
and the queue head don't need to reset the tail code. For that case,
a simple write to set the lock bit is enough as the queue head will
be the only one eligible to
v13->v14:
- Patches 1 & 2: Add queue_spin_unlock_wait() to accommodate commit
78bff1c86 from Oleg Nesterov.
- Fix the system hang problem when using PV qspinlock in an
over-committed guest due to a racing condition in the
pv_set_head_in_tail() function.
- Increase the MAYHALT_THRESHOLD
From: Peter Zijlstra
Because the qspinlock needs to touch a second cacheline (the per-cpu
mcs_nodes[]); add a pending bit and allow a single in-word spinner
before we punt to the second cacheline.
It is possible so observe the pending bit without the locked bit when
the last owner has just relea
From: Peter Zijlstra
When we detect a hypervisor (!paravirt, see qspinlock paravirt support
patches), revert to a simple test-and-set lock to avoid the horrors
of queue preemption.
Signed-off-by: Peter Zijlstra
Signed-off-by: Waiman Long
---
arch/x86/include/asm/qspinlock.h | 14 +++
This patch introduces a new generic queue spinlock implementation that
can serve as an alternative to the default ticket spinlock. Compared
with the ticket spinlock, this queue spinlock should be almost as fair
as the ticket spinlock. It has about the same speed in single-thread
and it can be much
On 13/01/15 08:14, Imre Palik wrote:
> From: "Palik, Imre"
>
> In Dom0's the use of the TSC clocksource (whenever it is stable enough to
> be used) instead of the Xen clocksource should not cause any issues, as
> Dom0 VMs never live-migrated. The TSC clocksource is somewhat more
> efficient than
> BTW, I notice that you have hardcoded the GIC addresses and various
> interrupt sources. We do not make any guarantees about the guest
> virtual platform memory or interrupt layout beyond committing to
> correctly describing them in the Device Tree Blob which is passed to
> the guest kernel at st
Ian Campbell writes ("[PATCH OSSTEST v2 18/18] WIP: libvirt: migration +
save/restore support."):
> Note that this remains stubbed out, since making it actually work
> requires more work (i.e. I need to figure out what is involved, seem
> to need TLS and a CA etc...)
How annoying.
> NB haven't m
Ian Campbell writes ("[PATCH OSSTEST v2 17/18] ts-guest-start: Use
guest_create"):
> This allows us to abolish CfgPathVar which was inconsistently used,
> appears redundant with $gho->{CfgPath} and in any case never set to
> anything other than 'cfgpath'.
>
> I suppose it was intended to deal wit
Ian Campbell writes ("[PATCH OSSTEST v2 11/18] Toolstack: Refactor migration
support check."):
> Not implemented for libvirt (the check itself that is, the hook is present).
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http
On Mon, Jan 19, 2015 at 12:41:24PM +0800, Jiang Liu wrote:
>
> On 2015/1/17 2:13, Konrad Rzeszutek Wilk wrote:
> > On Thu, Jan 15, 2015 at 09:04:35PM +0800, Jiang Liu wrote:
>
> >>
> >> Note: we need to test this patch on those special AMD systems which
> >> override normal SCI GSI (9) with stran
Ian Campbell writes ("[PATCH OSSTEST v2 13/18] Toolstack: Refactor save/restore
support"):
> Still stubbed out for libvirt.
...
> +sub restore ($) {
> +my ($self,$gho,$f,$cfg,$to) = @_;
> +my $ho = $self->{Host};
> +my $gn = $gho->{Name};
> +target_cmd_root($ho,
> +
Ian Campbell writes ("[PATCH OSSTEST v2 15/18] libvirt: Implement
shutdown_wait"):
> virsh does not include a --wait option to shutdown as xl and xm do, so
> we implement it by hand.
>
> Needs new guest_await_destroy helper. Note the guest_await_shutdown
> requires on_shutdown='preserve'
I see t
Ian Campbell writes ("[PATCH OSSTEST v2 12/18] Toolstack: Refactor migration
support."):
> Note that since the previous patch arranges for
> ts-migration-support-check to continue to fail for libvirt the libvirt
> code is not actually called yet (and will die if it is). This patch is
> mainly incl
Ian Campbell writes ("[PATCH OSSTEST v2 14/18] libvirt: Implement initscript
restart which has some hope of working."):
...
>restart)
> - stop
> - start
> + [ "$VERBOSE" != no ] && log_daemon_msg "Restarting $DESC" "$DAEMON"
> + start-stop-daemon --oknodo --stop --pidfile $PIDF
On Tue, Jan 20, 2015 at 09:00:36AM +, Jan Beulich wrote:
> >>> On 05.01.15 at 21:08, wrote:
> > = Timeline =
> >
> > Xen 4.5 is a 10 month release. The dates are:
> >
> > * Feature Freeze: 24th September 2014
> > * First RC: 24th October [Friday!]
> > * RC2: Nov 11th
> > * RC2 Test-day: Nov
Ian Campbell writes ("[PATCH OSSTEST v2 10/18] Toolstack: Refactor shutdown
support"):
> +sub shutdown_wait ($$) {
> +my ($self,$gho) = @_;
> +my $ho = $self->{Host};
> +my $gn = $gho->{Name};
> +target_cmd_root($ho,"$self->{Command} shutdown -w $gn", 200);
I think the timeout sho
Ian Campbell writes ("[PATCH OSSTEST v2 16/18] Toolstack: Remove Command field
for all toolstacks."):
> Nothing in generic code uses this now, so remove.
>
> xl+xend retain as _Command for internal use only.
Acked-by: Ian Jackson
Although personally I wouldn't bother with the rename.
Ian.
__
Ian Campbell writes ("[PATCH OSSTEST v2 07/18] TestSupport: guest_create takes
a $ho."):
> And looks up the toolstack from it.
...
> sub guest_create ($$) {
> -my ($gho,$toolstack) = @_;
> -target_cmd_root($gho->{Host}, "$toolstack create $gho->{CfgPath}", 100);
> +my ($ho,$gho) = @_;
Ian Campbell writes ("[PATCH OSSTEST v2 09/18] Toolstack: Refactor consolecmd
handling"):
...
> diff --git a/Osstest/Toolstack/xend.pm b/Osstest/Toolstack/xend.pm
> index c921c20..896d949 100644
> --- a/Osstest/Toolstack/xend.pm
> +++ b/Osstest/Toolstack/xend.pm
> @@ -36,5 +36,6 @@ sub new {
> #
On 20/01/15 17:05, Roger Pau Monne wrote:
> Prevent Dom0 from accessing HPET MMIO region by adding the HPET mfn to the
> list of read-only memory regions.
>
> Signed-off-by: Roger Pau Monné
> Cc: Jan Beulich
> Cc: Andrew Cooper
Please introduce a command line parameter to control this, but
defa
Ian Campbell writes ("[PATCH OSSTEST v2 08/18] Toolstack: Refactor guest
lifecycle."):
> Implement destory/create as per toolstack methods, including implementing the
> libvirt version which previously didn't work. To do this we use the virsh
> capability to convert an xl/xm style config file into
Ian Campbell writes ("[PATCH OSSTEST v2 06/18] TestSupport: always use xl for
generic operations."):
> For several operations in TestSupport.pm the actual toolstack isn't really
> relevant, since we want info straight from Xen. For simplicity just use xl (or
> xm) in these cases, to avoid needing
Ian Campbell writes ("[PATCH OSSTEST v2 04/18] ts-rumpuserxen-demo-xenstorels:
Use standard functions for things"):
> Specifically guest_create and guest_find_domid.
Acked-by: Ian Jackson
(Not sure why I did it like that.)
Ian.
___
Xen-devel mailing
Ian Campbell writes ("[PATCH OSSTEST v2 03/18] Pass host to toolstack()"):
> This will be needed in a future patch.
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Signed-off-by: David Vrabel
---
xen/common/grant_table.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/xen/common/grant_table.c b/xen/common/grant_table.c
index fe52b63..fb9d8f7 100644
--- a/xen/common/grant_table.c
+++ b/xen/common/grant_table.c
@@ -1882,7 +188
Netback tries (where possible) to minimize the number of copy ops in
the to-guest direction (since acquiring a page is expensive) this
reduces the number acquire operations at the expensive of more Rx
slots and more frags in the guests.
By deferring the release of the pages we can optimize the cas
On 20/01/15 17:05, Roger Pau Monne wrote:
> Check that MMIO regions added to PVH Dom0 are allowed. Previously a PVH Dom0
> would have access to the full MMIO range.
>
> Signed-off-by: Roger Pau Monné
> Cc: Jan Beulich
> Cc: Andrew Cooper
> ---
> Changes since v1:
> - Use the newly introduced p2
Acquiring a page for the source or destination of a grant copy is an
expensive operation. A common use case is for two adjacent grant copy
ops to operate on either the same source or the same destination page.
Instead of always acquiring and releasing destination and source pages
for each operati
Ian Campbell writes ("[PATCH OSSTEST v2 05/18] Toolstack: use
get_host_method_object() to manage toolstack selection"):
> This will allow us to more easily have per-toolstack methods etc.
>
> The previous hash of toolstack parameters is now a blessed object. For
> now the callers don't need to ch
On 20/01/15 17:57, Ian Campbell wrote:
> On Tue, 2015-01-20 at 17:41 +, Julien Grall wrote:
>> Hi Ian,
>>
>> On 20/01/15 15:57, Ian Campbell wrote:
>>> On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
In general, it's not necessary/important to check the size.
>>>
>>> Only if the doc
Ian Campbell writes ("Outstanding OSSTEST patch series"):
> support for ARM32 arndale and cubietruck platforms
> v3 at <1416505070.26869.2.ca...@citrix.com>
...
> I'm not sure if you were waiting for v4 with just the commit
> logs rewrapped or not. I have that locally if you
Much of the grant copy operation is identical for the source and
destination buffers. Refactor the code into per-buffer functions.
Signed-off-by: David Vrabel
---
xen/common/grant_table.c | 286 +-
xen/include/public/grant_table.h |2 +-
2 files
Ian Campbell writes ("[PATCH OSSTEST v2 02/18] ts-logs-capture: Collect some
libvirt logs and capabilities"):
> Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Ian Campbell writes ("[PATCH OSSTEST v2 01/18] apt: lock osstest's usages of
apt-get against each other"):
> Currently we rely on all apt-get invocations being in a single
> ts-xen-build-prep job which can't run on a shared host.
>
> That is a bit inflexible so instead use our own lock. We wait
>
On 01/20/2015 12:47 AM, Jan Beulich wrote:
On 19.01.15 at 22:54, wrote:
>> There's also the issue that access permissions
>> are soft state and can be reverted to default in certain cases.
>
> Some instances of which have got removed during the 4.5 cycle,
> and at least some of the remaining
On Tue, 2015-01-20 at 17:41 +, Julien Grall wrote:
> Hi Ian,
>
> On 20/01/15 15:57, Ian Campbell wrote:
> > On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
> >> In general, it's not necessary/important to check the size.
> >
> > Only if the docs say this register can be accessed by a p
On 20/01/15 11:08, Jan Beulich wrote:
> ..., yielding better code.
>
> Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On 20/01/15 11:07, Jan Beulich wrote:
> Most of them have been unused since the dropping of 32-bit support, and
> the few remaining cases are more efficiently dealt with using a generic
> macro (and probably things should have been done that way from the
> beginning).
>
> Signed-off-by: Jan Beulich
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Xen Security Advisory CVE-2014-8594 / XSA-109
version 4
Insufficient restrictions on certain MMU update hypercalls
UPDATES IN VERSION 4
Impact on applicable affected systems is
On 20/01/15 11:06, Jan Beulich wrote:
> A few relevant control state fields did not get dumped so far; in
> particular, VM_ENTRY_INSTRUCTION_LEN got printed twice (instead of also
> printing VM_EXIT_INSTRUCTION_LEN). Where suitable (to reduce the amount
> of output) make some of the dumping conditi
On 20/01/15 17:41, Julien Grall wrote:
> Hi Ian,
>
> On 20/01/15 15:57, Ian Campbell wrote:
>> On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
>>> In general, it's not necessary/important to check the size.
>>
>> Only if the docs say this register can be accessed by a partial
>> read/write,
branch xen-unstable
xen branch xen-unstable
job build-amd64-libvirt
test libvirt-build
Tree: libvirt git://libvirt.org/libvirt.git
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
Tree: xen git://xenbits.xen.org/xen
Hi Ian,
On 20/01/15 16:05, Ian Campbell wrote:
> On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
>> Also remove vGICv3 in the message log as gdprintk already print the name
>> of the file.
>
> Please mention that the switch to gdprintk is how/where the domain/vcpu
> is added, e.g. by addin
On 20/01/15 11:06, Jan Beulich wrote:
> A few host state fields did not get dumped so far. Where suitable (to
> reduce the amount of output) make some of the dumping conditional upon
> guest settings (this isn't required for correctness as vmr() already
> uses __vmread_safe(), i.e. it is fine to ac
Hi Ian,
On 20/01/15 16:00, Ian Campbell wrote:
> On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
>> The current vGIC v3 driver doesn't fully implement GICv3 spec:
>> - GICv3 backward compatibility is not supported (GICD_CTLR.ARE = 0)
>
> I think you meant GICv2 here as you did in the c
Check that MMIO regions added to PVH Dom0 are allowed. Previously a PVH Dom0
would have access to the full MMIO range.
Signed-off-by: Roger Pau Monné
Cc: Jan Beulich
Cc: Andrew Cooper
---
Changes since v1:
- Use the newly introduced p2m_access_t to set the access type.
- Don't add a next labe
This series aims to prevent PVH Dom0 from accessing MMIO regions of
devices that are used by Xen.
Thanks for the review, Roger.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Hi Ian,
On 20/01/15 15:57, Ian Campbell wrote:
> On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
>> In general, it's not necessary/important to check the size.
>
> Only if the docs say this register can be accessed by a partial
> read/write, or if it is implementation defined what the resu
On 20/01/15 11:05, Jan Beulich wrote:
> Several guest state fields did not get dumped so far. Where suitable
> (to reduce the amount of output) make some of the dumping conditional
> upon guest settings (this isn't required for correctness as vmr()
> already uses __vmread_safe(), i.e. it is fine to
Preparatory change that allows setting the access type to
set_mmio_p2m_entry.
Signed-off-by: Roger Pau Monné
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Jun Nakajima
Cc: Eddie Dong
Cc: Kevin Tian
Cc: Tim Deegan
---
xen/arch/x86/domain_build.c | 3 ++-
xen/arch/x86/hvm/vmx/vmx.c | 2 +-
xen/ar
Prevent Dom0 from accessing HPET MMIO region by adding the HPET mfn to the
list of read-only memory regions.
Signed-off-by: Roger Pau Monné
Cc: Jan Beulich
Cc: Andrew Cooper
---
Changes since v1:
- Instead of completely blocking access to the HPET mfn, set it as
read-only.
---
xen/arch/x86
Hi Ian,
On 20/01/15 15:51, Ian Campbell wrote:
> On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
>> As backward GICv2 compatibility is not supported in the VGICv3 driver,
>> the bit ARE_NS should be set at any time.
>
> Looking at the docs, I think you mean it is RAO/WI if GICv2 compat is
Hi Ian,
On 20/01/15 15:34, Ian Campbell wrote:
> On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
>> +unsigned int order;
>> +
>> if ( dabt.size != DABT_WORD ) goto bad_width;
>> /* No secure world support for guests. */
>> *r = (((v->domain->max_vcpus << 5
On 20/01/15 16:40, Jan Beulich wrote:
On 20.01.15 at 15:28, wrote:
>> On 19/01/15 17:02, Jan Beulich wrote:
>> On 13.01.15 at 15:25, wrote:
--- a/xen/drivers/passthrough/device_tree.c
+++ b/xen/drivers/passthrough/device_tree.c
@@ -41,6 +41,10 @@ int iommu_assign_dt_device
Jan,
I have announced it on xen-users, xen-announce, the blog and we have had the
press release
I had assumed that Konrad announced on xen-devel
Lars
On 20 Jan 2015, at 09:00, Jan Beulich wrote:
On 05.01.15 at 21:08, wrote:
>> = Timeline =
>>
>> Xen 4.5 is a 10 month release. The dates
On Tue, 2015-01-20 at 14:21 +, Ian Jackson wrote:
> I am 100% in agreement with Roger's proposal. I think we should
> extend this principle to as much of the guest ABI as possible, not
> just PV protocols - it would be good to do it for guest-visible
> hypervisor and tools ABIs too.
Agreed, b
Dave Scott writes ("Cancelling asynchronous operations in libxl"):
> I’ve re-read the thread from Nov 2013: (2013!)
> http://lists.xen.org/archives/html/xen-devel/2013-11/msg01176.html
> and found it quite thought-provoking.
Thanks.
However, I think the message you really want is
From: Ian Jac
On Tue, 2015-01-20 at 11:04 -0500, Boris Ostrovsky wrote:
> On 01/20/2015 10:21 AM, Ian Campbell wrote:
> > On Tue, 2015-01-20 at 10:15 -0500, Boris Ostrovsky wrote:
> diff --git a/tools/libxl/libxl_linux.c b/tools/libxl/libxl_linux.c
> index ea5d8c1..07428c0 100644
> --- a/tools/lib
>>> On 20.01.15 at 15:37, wrote:
> On 20/01/15 09:34, Jan Beulich wrote:
> On 13.01.15 at 15:25, wrote:
>>> --- a/xen/drivers/passthrough/iommu.c
>>> +++ b/xen/drivers/passthrough/iommu.c
>>> @@ -337,6 +337,13 @@ int iommu_do_domctl(
>>> ret = iommu_do_pci_domctl(domctl, d, u_domctl);
>>
>>> On 20.01.15 at 15:30, wrote:
> Hi Jan,
>
> On 20/01/15 09:19, Jan Beulich wrote:
> On 13.01.15 at 15:25, wrote:
>>> --- a/xen/include/xen/iommu.h
>>> +++ b/xen/include/xen/iommu.h
>>> @@ -117,7 +117,7 @@ void iommu_read_msi_from_ire(struct msi_desc *msi_desc,
> struct msi_msg *msg);
>>>
>>> On 20.01.15 at 15:28, wrote:
> On 19/01/15 17:02, Jan Beulich wrote:
> On 13.01.15 at 15:25, wrote:
>>> --- a/xen/drivers/passthrough/device_tree.c
>>> +++ b/xen/drivers/passthrough/device_tree.c
>>> @@ -41,6 +41,10 @@ int iommu_assign_dt_device(struct domain *d, struct
>>> dt_device_nod
On 01/20/2015 05:37 AM, Jan Beulich wrote:
On 05.01.15 at 22:43, wrote:
Changes in v17:
* Disable VPMU when unknown CPU vendor is detected (patch #2)
* Remove unnecessary vendor tests in vendor-specific init routines (patch #14)
* Remember first CPU that starts mode change and use it to stop th
On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
> This register is shared between every vCPUs and the lock was already
> taken for read.
>
> Signed-off-by: Julien Grall
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lists.xen.or
Dario Faggioli writes ("Re: [OSSTEST PATCH] make-flight: reorganize scheduling
related test jobs"):
> Yes, here it comes. Sorry for the delay (wasn't working for most of last
> week). Any better?
Brilliant, thanks. LGTM.
Acked-by: Ian Jackson
Ian.
On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
> Some registers, such as GICD_ITARGET0 can be read/write with different
> size.
>
> When the write is ignored only word-access is checked. This will lead to
> a domain crash if the guest is trying to access via byte-word.
>
> In general, it'
On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
> Also remove vGICv3 in the message log as gdprintk already print the name
> of the file.
Please mention that the switch to gdprintk is how/where the domain/vcpu
is added, e.g. by adding "... by switching to gdprintk" as the first
line of the
>>> On 20.01.15 at 15:00, wrote:
> On 20/01/15 13:48, Jan Beulich wrote:
> On 20.01.15 at 14:39, wrote:
>>> It is far nicer to work from a document than to worry how another
>>> compiler might change the structure.
>> Compilers have (almost, i.e. leaving aside bitfields) no freedom in laying
On Mon, 2015-01-19 at 16:29 +, Julien Grall wrote:
Please reference the switch to gdprintk being the mechanism for
achieving this, otherwise:
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/x
1 - 100 of 263 matches
Mail list logo
