Re: [Xen-devel] [PATCH for-4.10 v2] passthrough/vtd: Don't DMA to the stack in queue_invalidate_wait()

2017-10-23 Thread Andrew Cooper
On 23/10/2017 08:18, Jan Beulich wrote: On 20.10.17 at 19:55, wrote: >> On 20/10/17 08:12, Jan Beulich wrote: >> On 19.10.17 at 18:22, wrote: DMA-ing to the stack is generally considered bad practice. In this case, if >>

Re: [Xen-devel] [PATCH V3 15/29] x86/vvtd: Process interrupt remapping request

2017-10-23 Thread Chao Gao
On Fri, Oct 20, 2017 at 11:01:03AM +0100, Roger Pau Monné wrote: >On Fri, Oct 20, 2017 at 01:16:37PM +0800, Chao Gao wrote: >> On Thu, Oct 19, 2017 at 03:26:30PM +0100, Roger Pau Monné wrote: >> >On Thu, Sep 21, 2017 at 11:01:56PM -0400, Lan Tianyu wrote: >> >> +static void unmap_guest_page(void

Re: [Xen-devel] [PATCH v3 2/7] xsm: flask: change the dummy xsm policy and flask hook for map_gmfn_foregin

2017-10-23 Thread Jan Beulich
>>> On 22.10.17 at 13:21, wrote: > How about changing the policy to (c over d) && ((d over t) || (c over t))? > Given that (c over d) is a must, which is always checked somewhere higher > in the call stack as Daniel pointed out, permitting (d over t) or (c > over t)

Re: [Xen-devel] [PATCH for-4.10 v2] passthrough/vtd: Don't DMA to the stack in queue_invalidate_wait()

2017-10-23 Thread Jan Beulich
>>> On 20.10.17 at 19:55, wrote: > On 20/10/17 08:12, Jan Beulich wrote: > On 19.10.17 at 18:22, wrote: >>> DMA-ing to the stack is generally considered bad practice. In this case, >>> if > a >>> timeout occurs because of a sluggish

Re: [Xen-devel] [PATCH for-next] x86/VT-x: Don't use rdmsr() to fill HOST_SYSENTER_{CS, EIP}

2017-10-23 Thread Tian, Kevin
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com] > Sent: Friday, October 20, 2017 10:02 PM > > These are compile-time constants, and don't need to be read back from > hardware. > > Signed-off-by: Andrew Cooper Acked-by: Kevin Tian

Re: [Xen-devel] [PATCH for-4.10 v2] passthrough/vtd: Don't DMA to the stack in queue_invalidate_wait()

2017-10-23 Thread Tian, Kevin
> From: Tian, Kevin > Sent: Monday, October 23, 2017 3:05 PM > > > From: Andrew Cooper [mailto:andrew.coop...@citrix.com] > > Sent: Saturday, October 21, 2017 1:55 AM > > > > On 20/10/17 08:12, Jan Beulich wrote: > > On 19.10.17 at 18:22, wrote: > > >> DMA-ing to

Re: [Xen-devel] [PATCH for-4.10 v2] passthrough/vtd: Don't DMA to the stack in queue_invalidate_wait()

2017-10-23 Thread Tian, Kevin
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com] > Sent: Saturday, October 21, 2017 1:55 AM > > On 20/10/17 08:12, Jan Beulich wrote: > On 19.10.17 at 18:22, wrote: > >> DMA-ing to the stack is generally considered bad practice. In this case, > >> if > a

[Xen-devel] [linux-linus test] 115067: regressions - trouble: broken/fail/pass

2017-10-23 Thread osstest service owner
flight 115067 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/115067/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-libvirt-pair broken test-amd64-i386-libvirt-pair 4

Re: [Xen-devel] [PATCH for-next] x86/VT-x: Don't rewrite HOST_TR_SELECTOR on every context switch

2017-10-23 Thread Tian, Kevin
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com] > Sent: Wednesday, October 18, 2017 1:16 AM > > TSS_ENTRY is a compile time constant, so HOST_TR_SELECTOR can be set > up during > VMCS construction and left alone thereafter, rather than rewriting it on > every > context switch. > >

<    1   2