On 11/08/2017 08:40 AM, Juergen Gross wrote:
> On 08/11/17 14:37, Boris Ostrovsky wrote:
>> On 11/08/2017 04:07 AM, Juergen Gross wrote:
>>> Booting a Xen PVH guest requires a special boot entry as it is
>>> mandatory to setup some Xen-specific interfaces rather early. When grub
>>> or OVMF are use
On 08/11/17 14:37, Boris Ostrovsky wrote:
> On 11/08/2017 04:07 AM, Juergen Gross wrote:
>> Booting a Xen PVH guest requires a special boot entry as it is
>> mandatory to setup some Xen-specific interfaces rather early. When grub
>> or OVMF are used as boot loaders, however, those will fill the boo
On 11/08/2017 04:07 AM, Juergen Gross wrote:
> Booting a Xen PVH guest requires a special boot entry as it is
> mandatory to setup some Xen-specific interfaces rather early. When grub
> or OVMF are used as boot loaders, however, those will fill the boot
> parameters in zeropage and there is no long
Booting a Xen PVH guest requires a special boot entry as it is
mandatory to setup some Xen-specific interfaces rather early. When grub
or OVMF are used as boot loaders, however, those will fill the boot
parameters in zeropage and there is no longer a need to do something
PVH specific in the early b
On 01/11/17 17:00, Boris Ostrovsky wrote:
> On 10/31/2017 06:03 PM, brian.wo...@amd.com wrote:
>> From: Brian Woods
>>
>> x86/svm: virtual VMLOAD/VMSAVE
>>
>> On AMD family 17h server processors, there is a feature called virtual
>> VMLOAD/VMSAVE. This allows a nested hypervisor to preform a VMLO
On 10/31/2017 06:03 PM, brian.wo...@amd.com wrote:
> From: Brian Woods
>
> x86/svm: virtual VMLOAD/VMSAVE
>
> On AMD family 17h server processors, there is a feature called virtual
> VMLOAD/VMSAVE. This allows a nested hypervisor to preform a VMLOAD or
> VMSAVE without needing to be intercepted b
From: Brian Woods
x86/svm: virtual VMLOAD/VMSAVE
On AMD family 17h server processors, there is a feature called virtual
VMLOAD/VMSAVE. This allows a nested hypervisor to preform a VMLOAD or
VMSAVE without needing to be intercepted by the host hypervisor.
Virtual VMLOAD/VMSAVE requires the host
On 20/10/17 15:11, Jan Beulich wrote:
1: fix GS-base-dirty determination
2: also show FS/GS base addresses when dumping registers
3: avoid FS/GS base reads
Patch 1 is a bug fix which should be strongly considered for 4.10.
Patch 2 has proven helpful in analyzing the original problem, so
would
1: fix GS-base-dirty determination
2: also show FS/GS base addresses when dumping registers
3: avoid FS/GS base reads
Patch 1 is a bug fix which should be strongly considered for 4.10.
Patch 2 has proven helpful in analyzing the original problem, so
would be nice to have upstream rather sooner tha
Hi Jan,
On 12/10/17 10:38, Jan Beulich wrote:
The first two patches are bug fixes and hence candidates for 4.10.
The 3rd is mostly cleanup, and hence intended only for after 4.10.
1: request page table page-in for the correct domain
2: fix do_update_va_mapping_otherdomain() wrt translated domai
The first two patches are bug fixes and hence candidates for 4.10.
The 3rd is mostly cleanup, and hence intended only for after 4.10.
1: request page table page-in for the correct domain
2: fix do_update_va_mapping_otherdomain() wrt translated domains
3: tighten MMU_*PT_UPDATE* check and combine e
This series is mostly cleanup, base on code observations when working on my
comprehensive XTF pagetable test, running in unpaged modes. I've double
checked the behaviour HAP and Shadow modes, with and without the unrestricted
guest feature, on Haswell and Skylake-S hardware.
Andrew Cooper (3):
On Tue, 2017-09-26 at 14:43 +, Owen Smith wrote:
> Improve the input device model in xenfb, by updating the
> Qemu input handlers and adding a feature to allow for
> raw (unscaled) absolute coordinates to be represented.
>
> By using a reverse mapping call, the Linux input.h #defines
> are not
Improve the input device model in xenfb, by updating the
Qemu input handlers and adding a feature to allow for
raw (unscaled) absolute coordinates to be represented.
By using a reverse mapping call, the Linux input.h #defines
are not pulled into xenfb, and so should remove the compiler
warnings re
Wei Liu (3):
libxl: use libxl__read_xenstore_check in vtpm function
libxl: use libxl__read_xenstore_check in vdispl function
xl: avoid leaking memory in vdispl parser
tools/libxl/libxl_vdispl.c | 7 +--
tools/libxl/libxl_vtpm.c | 6 --
tools/xl/xl_parse.c| 2 ++
3 files ch
Hello,
this series is the followup of my previous RCU series. It contains:
- the patch that makes the period of the RCU idle timer configurable, via a Xen
boot time parameter, as suggested by Jan, during review of the original series
(patch 2);
- the patch that makse the period of the RCU idle
Expose xs_fileno() and xs_check_watch() to Python. These functions
make it posible to write event-driven Xenstore clients in Python:
#!/usr/bin/env python
import xen.lowlevel.xs
import sys
import errno
from select import select
import time
# Connect to XenStore and set wat
On 11/09/17 10:32, Jan Beulich wrote:
> 1: VMX: convert CPU family numbers to hex
> 2: VMX: add new CPU families to LBR handling
> 3: x86/cpuidle: add new CPU families
>
> Signed-off-by: Jan Beulich
>
Acked-by: Andrew Cooper
___
Xen-devel mailing list
1: VMX: convert CPU family numbers to hex
2: VMX: add new CPU families to LBR handling
3: x86/cpuidle: add new CPU families
Signed-off-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Wei Liu (3):
x86/mm: introduce trace point for mmio_ro emulation
x86/mm: don't wrap x86_emulate_ctxt in ptwr_emulate_ctxt
x86/mm: merge ptwr and mmio_ro page fault handlers
xen/arch/x86/mm.c| 325 +++
xen/arch/x86/traps.c | 20
Andrew Cooper (3):
gnttab: Drop the frame parameter from acquire_grant_for_copy()
gnttab: Drop the frame parameter from get_paged_frame()
gnttab: Drop the frame field from struct gnttab_copy_buf
xen/common/grant_table.c | 80 ++--
1 file changed,
All changes reduce the quantity of explicit mfn_t boxing/unboxing.
No functional change (confirmed by diffing the disassembly).
Andrew Cooper (3):
x86/mm: Replace opencoded forms of l?e_{get,from}_page()
x86/mm: Replace opencoded forms of map_l?t_from_l?e()
x86/mm: Introduce and use l?e_{ge
Wei Liu (3):
xen: move hvm save code under common to x86
xen: merge common hvm/irq.h into x86 hvm/irq.h
x86: switch to plain bool in passthrough code
xen/arch/x86/cpu/mcheck/vmce.c | 2 +-
xen/arch/x86/cpu/vpmu_amd.c | 2 +-
xen/arch/x86/hvm/save.c |
On 08/04/2017 07:36 AM, Juergen Gross wrote:
> Remove stuff no longer needed.
>
> Juergen Gross (3):
> xen: remove tests for pvh mode in pure pv paths
> xen: remove unused function xen_set_domain_pte()
> xen: remove not used trace functions
>
> arch/x86/include/asm/xen/page.h | 5 -
> a
Cleanup special cases of paravirt patching:
- Xen doesn't need a custom patching function, it can use
paravirt_patch_default()
- Remove lguest completely from the tree. A LKML mail asking for any
users 3 months ago did not reveal any need for keeping lguest [1].
- Remove vsmp paravirt suppor
Remove stuff no longer needed.
Juergen Gross (3):
xen: remove tests for pvh mode in pure pv paths
xen: remove unused function xen_set_domain_pte()
xen: remove not used trace functions
arch/x86/include/asm/xen/page.h | 5 -
arch/x86/xen/mmu_pv.c | 20
arc
On Mon, Jul 31, 2017 at 02:51:21PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH 0/3] Docs: consolidate release related documents"):
> > Wei Liu (3):
> > docs: consolidate release related documents
> > docs: add xen-release-management.pandoc
> > docs: hook up process/ to build system
>
Wei Liu writes ("[PATCH 0/3] Docs: consolidate release related documents"):
> Wei Liu (3):
> docs: consolidate release related documents
> docs: add xen-release-management.pandoc
> docs: hook up process/ to build system
FWIW,
Acked-by: Ian Jackson
However, AFAICT the mean reason this does
Wei Liu (3):
docs: consolidate release related documents
docs: add xen-release-management.pandoc
docs: hook up process/ to build system
docs/Makefile | 2 +-
{misc => docs/process}/branching-checklist.txt | 0
{misc => docs/process}/release-checklist.txt
This patch series fixes a regression introduced in 4.13-rc1: A Xen
HVM guest with KASLR enabled wouldn't boot any longer due to the usage
of __va() before kernel_randomize_memory() was called.
Juergen Gross (3):
x86: provide an init_mem_mapping hypervisor hook
xen: split up xen_hvm_init_shared
On 24/07/17 16:41, Wei Liu wrote:
> On Mon, Jul 24, 2017 at 04:22:52PM +0100, Wei Liu wrote:
>> On Mon, Jul 24, 2017 at 04:01:55PM +0100, Andrew Cooper wrote:
>>> On 24/07/17 15:44, Wei Liu wrote:
On Mon, Jul 24, 2017 at 03:25:22PM +0100, Andrew Cooper wrote:
> On 24/07/17 15:02, Wei Liu w
On Mon, Jul 24, 2017 at 04:22:52PM +0100, Wei Liu wrote:
> On Mon, Jul 24, 2017 at 04:01:55PM +0100, Andrew Cooper wrote:
> > On 24/07/17 15:44, Wei Liu wrote:
> > > On Mon, Jul 24, 2017 at 03:25:22PM +0100, Andrew Cooper wrote:
> > >> On 24/07/17 15:02, Wei Liu wrote:
> > >>> Wei Liu (3):
> > >>>
On Mon, Jul 24, 2017 at 04:01:55PM +0100, Andrew Cooper wrote:
> On 24/07/17 15:44, Wei Liu wrote:
> > On Mon, Jul 24, 2017 at 03:25:22PM +0100, Andrew Cooper wrote:
> >> On 24/07/17 15:02, Wei Liu wrote:
> >>> Wei Liu (3):
> >>> x86: nuke PV superpage option and code
> >>> tools: nuke superpag
On 24/07/17 15:44, Wei Liu wrote:
> On Mon, Jul 24, 2017 at 03:25:22PM +0100, Andrew Cooper wrote:
>> On 24/07/17 15:02, Wei Liu wrote:
>>> Wei Liu (3):
>>> x86: nuke PV superpage option and code
>>> tools: nuke superpage parameters in code
>>> docs: delete PV superpage option
>> If you are d
On Mon, Jul 24, 2017 at 03:25:22PM +0100, Andrew Cooper wrote:
> On 24/07/17 15:02, Wei Liu wrote:
> > Wei Liu (3):
> > x86: nuke PV superpage option and code
> > tools: nuke superpage parameters in code
> > docs: delete PV superpage option
>
> If you are doing this, can you modify
> xc_sr_s
On 24/07/17 15:02, Wei Liu wrote:
> Wei Liu (3):
> x86: nuke PV superpage option and code
> tools: nuke superpage parameters in code
> docs: delete PV superpage option
If you are doing this, can you modify
xc_sr_save_x86_pv.c:normalise_pagetable() to fail immediately if a
superpage is found.
Wei Liu (3):
x86: nuke PV superpage option and code
tools: nuke superpage parameters in code
docs: delete PV superpage option
docs/man/xl.conf.pod.5 | 3 -
docs/misc/xen-command-line.markdown | 7 -
tools/libxc/include/xenguest.h | 3 +-
tools/libxc/xc_nomigrate.c
No functional change, but the source code is less verbose.
Andrew Cooper (3):
x86/emul: Introduce build time assertions for struct segment_register
x86/hvm: Rearange check_segment() to use a switch statement
x86/emul: Drop segment_attributes_t
tools/fuzz/x86_instruction_emulator/fuzz-emul.
On 27 June 2017 at 23:04, Stefano Stabellini wrote:
> The following changes since commit 577caa2672ccde7352fda3ef17e44993de862f0e:
>
> Merge remote-tracking branch
> 'remotes/edgar/tags/edgar/mmio-exec-v2.for-upstream' into staging (2017-06-27
> 16:56:55 +0100)
>
> are available in the git rep
This patchset is to deal with MSI interrupt remapping request when guest
updates MSI registers.
Chao Gao (3):
i386/msi: Correct mask of destination ID in MSI address
xen-pt: bind/unbind interrupt remapping format MSI
msi: Handle remappable format interrupt request
configure
The following changes since commit 577caa2672ccde7352fda3ef17e44993de862f0e:
Merge remote-tracking branch
'remotes/edgar/tags/edgar/mmio-exec-v2.for-upstream' into staging (2017-06-27
16:56:55 +0100)
are available in the git repository at:
git://xenbits.xen.org/people/sstabellini/qemu-dm.
Some compilation fixes for GCC 7, done in Fedora 26 environment.
This isn't complete yet - some compilation issues are still there (more on it
in separate thread), but those patches do solve some problems.
Additionally Xen 4.6 - 4.8 (haven't checked others) require those patches to be
backported:
Paul Durrant (3):
xen-disk: only advertize feature-persistent if grant copy is not
available
xen-disk: add support for multi-page shared rings
xen-disk: use an IOThread per instance
hw/block/trace-events | 7 ++
hw/block/xen_disk.c | 200 -
On Sun, 4 Jun 2017, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 4 Jun 2017 22:45:54 +0200
>
> Three update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (3):
> Improve a size determination
> Delete an error message for a failed me
From: Markus Elfring
Date: Sun, 4 Jun 2017 22:45:54 +0200
Three update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Improve a size determination
Delete an error message for a failed memory allocation
Adjust one function call together with a vari
Hi all,
this small patch series fixes a couple of issues with ./raise test and
makes tests work on ARM (actually just busybox-pv for now, the others
are disabled).
Stefano Stabellini (3):
raisin: introduce TEST_KERNEL and TEST_INITRD
raisin: check for invalid initrds
raisin/arm
Hi Jan,
On 18/05/17 09:01, Jan Beulich wrote:
I think it would be good for 4.9 to build out of the box with this recently
released compiler version.
1: xmalloc: correct _xmalloc_array() indentation
2: x86: fix build with gcc 7
3: arm: fix build with gcc 7
Signed-off-by: Jan Beulich
For the
As the code stands right now, after DomU has enabled #VE using
HVMOP_altp2m_vcpu_enable_notify, all its pages have the #VE suppress bit
cleared, generating #VEs for any EPT violation. There is currently no
way to change the value of the #VE suppress bit for a page from a
domain; it can only be don
On 18/05/17 16:38, Roger Pau Monné wrote:
> On Tue, May 16, 2017 at 08:23:17AM +0200, Juergen Gross wrote:
>> Destroying a Xen guest domain while it was doing I/Os via xen-blkback
>> leaked several resources, including references of the guest's memory
>> pages.
>>
>> This patch series addresses tho
On Tue, May 16, 2017 at 08:23:17AM +0200, Juergen Gross wrote:
> Destroying a Xen guest domain while it was doing I/Os via xen-blkback
> leaked several resources, including references of the guest's memory
> pages.
>
> This patch series addresses those leaks by correcting usage of
> reference coun
>>> On 18.05.17 at 10:34, wrote:
> On 18/05/17 09:01, Jan Beulich wrote:
>> I think it would be good for 4.9 to build out of the box with this recently
>> released compiler version.
>
> I don't see the 3 patches on the ML. Is there any SMTP problem?
They should be there now (or really soon).
Ja
Hi Jan,
On 18/05/17 09:01, Jan Beulich wrote:
I think it would be good for 4.9 to build out of the box with this recently
released compiler version.
I don't see the 3 patches on the ML. Is there any SMTP problem?
1: xmalloc: correct _xmalloc_array() indentation
2: x86: fix build with gcc 7
3
I think it would be good for 4.9 to build out of the box with this recently
released compiler version.
1: xmalloc: correct _xmalloc_array() indentation
2: x86: fix build with gcc 7
3: arm: fix build with gcc 7
Signed-off-by: Jan Beulich
___
Xen-devel
On 2017-05-16 16:23, Juergen Gross wrote:
Destroying a Xen guest domain while it was doing I/Os via xen-blkback
leaked several resources, including references of the guest's memory
pages.
This patch series addresses those leaks by correcting usage of
reference counts and the sequence when to fre
Destroying a Xen guest domain while it was doing I/Os via xen-blkback
leaked several resources, including references of the guest's memory
pages.
This patch series addresses those leaks by correcting usage of
reference counts and the sequence when to free which resource.
The series applies on top
Hi Juergen,
On 08/05/17 08:00, Juergen Gross wrote:
There were some bits missing in docs/misc/xenstore.txt, so add them.
We might want to include this in 4.9, but I'm not feeling really
strong about this.
I think any documentation patch should go in the release. Better
documentation will mak
There were some bits missing in docs/misc/xenstore.txt, so add them.
We might want to include this in 4.9, but I'm not feeling really
strong about this.
Resending with correct email address of Julien.
Juergen Gross (3):
docs: specify endianess of xenstore protocol header
docs: add DIRECTORY_
There were some bits missing in docs/misc/xenstore.txt, so add them.
We might want to include this in 4.9, but I'm not feeling really
strong about this.
Juergen Gross (3):
docs: specify endianess of xenstore protocol header
docs: add DIRECTORY_PART specification do xenstore protocol doc
doc
Hi all,
This small patch series ensure that Xen will not die when receiving unknown
trap from the guests. I am not aware of any issue with platform we currently
support, so I am not sure whether it would be Xen 4.9 material.
Cheers,
Julien Grall (3):
xen/arm: arm32: Rename the trap to the corr
Hi Juergen,
On 02/05/17 10:30, Juergen Gross wrote:
On 02/05/17 11:08, Julien Grall wrote:
Hi all,
It looks like the series has fully been acked, can someone merge this
into xentip?
As I already wrote: patch 1 doesn't apply any longer.
As there were other conflicts between xentip and Linus'
On 24/04/17 19:58, Julien Grall wrote:
> Hi all,
>
> This small patch series implements EFI reset_system callback when using EFI
> Xen. Without this, it will not be possible to reboot/power off ARM64 DOM0
> when using ACPI.
>
> Cheers,
>
> Cc: Boris Ostrovsky
> Cc: Juergen Gross
Series rebase
On 02/05/17 11:08, Julien Grall wrote:
> Hi all,
>
> It looks like the series has fully been acked, can someone merge this
> into xentip?
As I already wrote: patch 1 doesn't apply any longer.
As there were other conflicts between xentip and Linus' tree I'm doing
a rebase of for-linus-4.12 right
Hi all,
It looks like the series has fully been acked, can someone merge this
into xentip?
Cheers,
On 04/24/2017 06:58 PM, Julien Grall wrote:
Hi all,
This small patch series implements EFI reset_system callback when using EFI
Xen. Without this, it will not be possible to reboot/power off A
Hi all,
This small patch series implements EFI reset_system callback when using EFI
Xen. Without this, it will not be possible to reboot/power off ARM64 DOM0
when using ACPI.
Cheers,
Cc: Boris Ostrovsky
Cc: Juergen Gross
Julien Grall (3):
xen: Export xen_reboot
arm/xen: Consolidate calls
Patch 1 brings recently added code in line with what we did switch
other code to during this dev cycle. Patch 2 is at least a latent bug fix.
Patch 3 is merely improving debuggability, so other than the first two
I'm not sure it qualifies for 4.9.
This is all fallout from re-basing my UMIP emulati
Hi,
When developing PVH for OVMF, I've used the lapic timer. It turns out that the
way it is used by OVMF did not work with Xen [1]. I tried to find out how
real-hw behave, and write a XTF tests [2]. And this patch series tries to fix
the behavior of the vlapic timer.
About the TSC-deadline mode,
On 22/03/17 16:17, Alex Thorlton wrote:
> On Tue, Mar 21, 2017 at 02:10:20PM +0100, Juergen Gross wrote:
>> This patch series is the first part for adding support of large EFI
>> memory maps (> the current limit of 128 entries) while reducing
>> trampoline size.
>>
>> I'm not posting the final patc
On Tue, Mar 21, 2017 at 02:10:20PM +0100, Juergen Gross wrote:
> This patch series is the first part for adding support of large EFI
> memory maps (> the current limit of 128 entries) while reducing
> trampoline size.
>
> I'm not posting the final patch for making the trampoline size
> reduction e
On Tue, Mar 21, 2017 at 02:10:20PM +0100, Juergen Gross wrote:
> This patch series is the first part for adding support of large EFI
> memory maps (> the current limit of 128 entries) while reducing
> trampoline size.
>
> I'm not posting the final patch for making the trampoline size
> reduction ef
This patch series is the first part for adding support of large EFI
memory maps (> the current limit of 128 entries) while reducing
trampoline size.
I'm not posting the final patch for making the trampoline size
reduction effective in order not to add major rebase work to Daniel's
multiboot2 serie
On Fri, 17 Mar 2017, Dario Faggioli wrote:
> Hello,
>
> This patch series implements what I call the 'null' scheduler.
>
> It's a very simple, very static scheduling posicy that always schedules the
> same vCPU(s) on the same pCPU(s). That's it.
>
> If there are less vCPUs than pCPUs, some of t
Hello,
This patch series implements what I call the 'null' scheduler.
It's a very simple, very static scheduling posicy that always schedules the
same vCPU(s) on the same pCPU(s). That's it.
If there are less vCPUs than pCPUs, some of the pCPUs are _always_ idle. If
there are more, some vCPUs
Hi all,
This patch series is fixing a potential bug when multiple vCPU of a guest is
running on the same pCPU. See patch #3 for all the details.
Regards,
Julien Grall (3):
xen/arm: hvm_domain does not need to be cacheline aligned
xen/arm: Introduce INVALID_VCPU_ID
xen/arm: p2m: Perform loc
This is concluding the exercise, perhaps with the exception of seeing
whether some of the auxiliary stuff added to the public header can
now be removed again (which may require tweaking some of the
scripts parsing the headers).
1: x86emul: switch away from temporary 32-bit register names
2: x86/hy
Hello,
This patch series removes the PVHv1 code, both from the hypervisor and the
tools, and also gets rid of the has_hvm_container_{domain/vcpu} macro, since
from Xen's point of view there are only two types of guests: PV or HVM.
Last patch is a minor code movement to have all the domain build P
Wei Liu (3):
fuzz/x86emul: avoid race in link farm rune
x86emul/test: avoid race in link farm rune
gitignore: ignore asm soft link in fuzz and x86emul test
.gitignore | 2 ++
tools/fuzz/x86_instruction_emulator/Makefile | 8 ++--
tools/tests/x86_emulato
The first two patches fix bugs and the last one moves inclusion of vpmu.h
from vmcs.h to domain.h
Boris Ostrovsky (3):
x86/vpmu: Calculate vpmu_enabled() based on vpmu_mode value
x86/vpmu: Decrement vpmu_count early in vpmu_destroy()
x86: Adjust which files need vpmu.h
xen/arch/x86/cpu/vpm
This patch series follows on from my recent Xen series [1], to provide
support in privcmd for de-privileging of device emulators.
[1] https://lists.xen.org/archives/html/xen-devel/2017-01/msg02558.html
Paul Durrant (3):
xen/privcmd: return -ENOSYS for unimplemented IOCTLs
xen/privcmd: Add IOC
These patches modify the implementation of Xen HVM disk unplug.
Paul Durrant (3):
xen-platform: re-structure unplug_disks
xen-platform: add support for unplugging NVMe disks...
xen-platform: add missing disk unplug option
hw/i386/xen/xen_platform.c | 50 +++-
The xenbus driver used for communication with Xenstore (all kernel
accesses to Xenstore and in case of Xenstore living in another domain
all accesses of the local domain to Xenstore) is rather simple
especially regarding multiple concurrent accesses: they are just being
serialized in spite of Xenst
Do some minor bug fixes and cleanup of xenbus driver.
Juergen Gross (3):
xen: xenbus driver must not accept invalid transaction ids
xen: return xenstore command failures via response instead of rc
xen: remove stale xs_input_avail() from header
drivers/xen/xenbus/xenbus_comms.h| 1
I think this then completes the set of simple move instructions the
emulator supports; the next step would then be to fully support
the SSEn/AVXn instruction sets.
1: support load forms of {,V}MOV{D,Q}
2: support {,V}LDDQU
3: support {,V}MOVNTDQA
Signed-off-by: Jan Beulich
This patchset fixes bugs and adds missing checks in nvmx_handle_vmxon(),
in order to make it more consistent to Intel SDM (section "VMXON - Enter
VMX Operation" in Vol 3).
Haozhong Zhang (3):
vvmx: set vmxon_region_pa of vcpu out of VMX operation to an invalid address
vvmx: return VMfail to L1
These patches are grouped together merely because of contextual
dependencies.
1: correct EFLAGS.TF handling
2: conditionally clear BNDn for branches
3: some REX related polishing
Signed-off-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.x
1: make tlbflush_filter()'s first parameter a pointer
2: VT-d: correct dma_msi_set_affinity()
3: x86: introduce and use scratch CPU mask
Signed-off-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
1: introduce hvm_get_cpl() and respective hook
2: support (emulate) UMIP
3: prefer structure assignment for seg reg copying
Signed-off-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Because of new version COLO has been merged by QEMU,
Some codes has changed by community comments.
So, we must update Xen COLO codes to support latest qemu.
Zhang Chen (3):
Don't create default ioreq server
Add Xen colo support for qemu-upstream colo codes
Add COLO replication top-id support
On Tue, Nov 22, 2016 at 06:51:27AM -0700, Jan Beulich wrote:
> 1: limit writes to incoming TSS during task switch
> 2: limit writes to outgoing TSS during task switch
> 3: correct error code writing during task switch
>
> Signed-off-by: Jan Beulich
>
Release-acked-by: Wei Liu
1: fix quad word bufioreq handling
2: slightly simplify bufioreq handling
3: ignore direction in bufioreq handling
Signed-off-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
1: limit writes to incoming TSS during task switch
2: limit writes to outgoing TSS during task switch
3: correct error code writing during task switch
Signed-off-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/
Hello,
Marek Marczykowski-Górecki, on Tue 18 Oct 2016 03:53:30 +0200, wrote:
> This series is follow up to previous attempts to fix this. Related threads:
> - http://markmail.org/thread/dwjcdfk3y7s5c5kl "PCI passthrough with
> stubdomain"
> - http://xen.markmail.org/thread/l7tvqcxbiyc2grvr "Jso
This series is follow up to previous attempts to fix this. Related threads:
- http://markmail.org/thread/dwjcdfk3y7s5c5kl "PCI passthrough with stubdomain"
- http://xen.markmail.org/thread/l7tvqcxbiyc2grvr "Json config and stubdomain"
With those patches applied, HVM finally have PCI devices work
On Fri, 14 Oct 2016, Jan Beulich wrote:
> >>> On 14.10.16 at 11:59, wrote:
> > On 14/10/16 07:36, Jan Beulich wrote:
> > On 14.10.16 at 02:58, wrote:
> >>> On Fri, 14 Oct 2016, Andrew Cooper wrote:
> There should be a high barrier to "Supported" status, because the cost
> of getting
On Fri, 14 Oct 2016, George Dunlap wrote:
> On 14/10/16 07:36, Jan Beulich wrote:
> On 14.10.16 at 02:58, wrote:
> >> On Fri, 14 Oct 2016, Andrew Cooper wrote:
> >>> There should be a high barrier to "Supported" status, because the cost
> >>> of getting it wrong is equally high. However, the
>>> On 14.10.16 at 11:59, wrote:
> On 14/10/16 07:36, Jan Beulich wrote:
> On 14.10.16 at 02:58, wrote:
>>> On Fri, 14 Oct 2016, Andrew Cooper wrote:
There should be a high barrier to "Supported" status, because the cost
of getting it wrong is equally high. However, there are perfe
On 14/10/16 07:36, Jan Beulich wrote:
On 14.10.16 at 02:58, wrote:
>> On Fri, 14 Oct 2016, Andrew Cooper wrote:
>>> There should be a high barrier to "Supported" status, because the cost
>>> of getting it wrong is equally high. However, there are perfectly
>>> legitimate intermediate stages
On Thu, 2016-10-13 at 13:46 +0100, Wei Liu wrote:
> On Thu, Oct 13, 2016 at 01:44:28PM +0100, Dario Faggioli wrote:
> >
> > Ok, so, if that's the case, what's the process: resend (this patch)
> > --
> > or some other kind of formal request-- with secur...@xenproject.org
> > Cc-ed?
> >
>
> If you
>>> On 14.10.16 at 02:58, wrote:
> On Fri, 14 Oct 2016, Andrew Cooper wrote:
>> There should be a high barrier to "Supported" status, because the cost
>> of getting it wrong is equally high. However, there are perfectly
>> legitimate intermediate stages such as "Supported in these limited set
>>
On Fri, 14 Oct 2016, Andrew Cooper wrote:
> > I like the idea of keeping these info on pandoc on a git repo, like Lars
> > did with the governance.
>
> I should hasten to add that perhaps picking on the security team in
> isolation was a poor move on my part, for which I apologise. There are
> mul
On 13/10/2016 22:06, Stefano Stabellini wrote:
>
> Credit2 **Supperted**, instead of experimental.
Supperted? That's like supported right? ;p
It is fine for you to propose that a feature should be upgraded to
supported, and this is probably the best way to formally do
1 - 100 of 278 matches
Mail list logo