xAPIC mode

Hi, is testing xAPIC mode just a matter of having diff --git a/configs/qemu-vm.c b/configs/qemu-vm.c index e5a420a..6225be9 100644 --- a/configs/qemu-vm.c +++ b/configs/qemu-vm.c @@ -49,6 +49,7 @@ struct { .pci_mmconfig_end_bus = 0xff, .x86 = {

CONFIG_STRICT_DEVMEM and 'tools/jailhouse hardware check'

Hi, it seems recent kernel configs on distros (at least mine, on Fedora), come with CONFIG_STRICT_DEVMEM=y, what seems the cause of the following output: Feature Availability -- -- Number of CPUs > 1 ok Long mode

Inmates' access to cell state

Hi, what's the intention with the current design where inmates have access to cell_state (COMM_REGION_GENERIC_HEADER)? Is this safe? I was able to replicate what apic-demo.c does WRT that in a Zephyr binary as well, just to be sure. Isn't ./tools/jailhouse cell list or, better yet,

[PATCH v2 Resend] configs: TK1: Add XUSB_DEV and XUSB_PADCTL regions

Those regions must be mapped to the root cell if a XUSB device is connected. Signed-off-by: Ralf Ramsauer --- configs/jetson-tk1.c | 20 +--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/configs/jetson-tk1.c

Re: Problems with ivshmem-net on root cell

Am Wed, 16 Aug 2017 00:13:54 + schrieb "Pontes, Otavio" : > On Sun, 2017-08-06 at 07:58 -0400, Jan Kiszka wrote: > > On 2017-08-05 02:59, Pontes, Otavio wrote: > > > Hi, > > > > > > I am using jailhouse in an Intel x86 hardware and I am having some > > > problems