On 11/16/2012 06:07 AM, Marcelo Tosatti wrote:
>
> We want to expose the pvclock shared memory areas, which
> the hypervisor periodically updates, to userspace.
>
> For a linear mapping from userspace, it is necessary that
> entire page sized regions are used for array of pvclock
> structures.
On 11/16/2012 11:56 AM, Marcelo Tosatti wrote:
> On Fri, Nov 16, 2012 at 11:39:12AM +0800, Xiao Guangrong wrote:
>> On 11/16/2012 11:02 AM, Marcelo Tosatti wrote:
>>> On Thu, Nov 15, 2012 at 07:17:15AM +0800, Xiao Guangrong wrote:
On 11/14/2012 10:37 PM, Marcelo Tosatti wrote:
> On Tue, No
On Fri, Nov 16, 2012 at 11:39:12AM +0800, Xiao Guangrong wrote:
> On 11/16/2012 11:02 AM, Marcelo Tosatti wrote:
> > On Thu, Nov 15, 2012 at 07:17:15AM +0800, Xiao Guangrong wrote:
> >> On 11/14/2012 10:37 PM, Marcelo Tosatti wrote:
> >>> On Tue, Nov 13, 2012 at 04:26:16PM +0800, Xiao Guangrong wro
On 11/16/2012 11:02 AM, Marcelo Tosatti wrote:
> On Thu, Nov 15, 2012 at 07:17:15AM +0800, Xiao Guangrong wrote:
>> On 11/14/2012 10:37 PM, Marcelo Tosatti wrote:
>>> On Tue, Nov 13, 2012 at 04:26:16PM +0800, Xiao Guangrong wrote:
Hi Marcelo,
On 11/13/2012 07:10 AM, Marcelo Tosatti w
On Wed, Nov 14, 2012 at 10:36:21AM +0900, Yoshihiro YUNOMAE wrote:
> Hi All,
>
> The following patch set can make disordered trace data of a guest and a host
> sorted in chronological order.
>
> In a virtualization environment, it is difficult to analyze performance
> problems, such as a delay of
On Thu, Nov 15, 2012 at 07:17:15AM +0800, Xiao Guangrong wrote:
> On 11/14/2012 10:37 PM, Marcelo Tosatti wrote:
> > On Tue, Nov 13, 2012 at 04:26:16PM +0800, Xiao Guangrong wrote:
> >> Hi Marcelo,
> >>
> >> On 11/13/2012 07:10 AM, Marcelo Tosatti wrote:
> >>> On Mon, Nov 05, 2012 at 05:59:26PM +08
We want to expose the pvclock shared memory areas, which
the hypervisor periodically updates, to userspace.
For a linear mapping from userspace, it is necessary that
entire page sized regions are used for array of pvclock
structures.
There is no such guarantee with per cpu areas, therefore mov
As noted by Gleb, not advertising SSE2 support implies
no RDTSC barriers.
Signed-off-by: Marcelo Tosatti
Index: vsyscall/arch/x86/include/asm/pvclock.h
===
--- vsyscall.orig/arch/x86/include/asm/pvclock.h
+++ vsyscall/arch/x86/incl
CPUID.7.0.EBX[1]=1 indicates IA32_TSC_ADJUST MSR 0x3b is supported
Basic design is to emulate the MSR by allowing reads and writes to the
hypervisor vcpu specific locations to store the value of the emulated MSRs.
In this way the IA32_TSC_ADJUST value will be included in all reads to
the TSC MSR w
CPUID.7.0.EBX[1]=1 indicates IA32_TSC_ADJUST MSR 0x3b is supported
Basic design is to emulate the MSR by allowing reads and writes to a guest
vcpu specific location to store the value of the emulated MSR while adding
the value to the vmcs tsc_offset. In this way the IA32_TSC_ADJUST value will
be i
In order to track who initiated the call (host or guest) to modify an msr
value I have changed function call parameters along the call path. The
specific change is to add a struct pointer parameter that points to (index,
data, caller) information rather than having this information passed as
indivi
Adding Gleb.
This is a resend of the patches for TSC_ADJUST functionality. The two KVM
patches and an additional QEMU-KVM patch
together provide this support.
Will Auld (2):
Add code to track call origin for msr assignment.
Enabling IA32_TSC_ADJUST for KVM guest VM support
arch/x86/inclu
On Fri, 2012-11-16 at 00:43 +0800, Jiang Liu wrote:
> On error recovery path in function vfio_create_group(), it should
> unregister the IOMMU notifier for the new VFIO group. Otherwise it may
> cause invalid memory access later when handling bus notifications.
>
> Signed-off-by: Jiang Liu
> ---
On error recovery path in function vfio_create_group(), it should
unregister the IOMMU notifier for the new VFIO group. Otherwise it may
cause invalid memory access later when handling bus notifications.
Signed-off-by: Jiang Liu
---
drivers/vfio/vfio.c | 31 +++
1 f
Comments from dev_driver_string(),
/* dev->driver can change to NULL underneath us because of unbinding,
* so be careful about accessing it.
*/
So use ACCESS_ONCE() to guard access to dev->driver field.
Signed-off-by: Jiang Liu
---
drivers/vfio/vfio.c |3 ++-
1 file changed, 2 insertions(
The two labels for error recovery in function vfio_pci_init() is out of
order, so fix it.
Signed-off-by: Jiang Liu
---
drivers/vfio/pci/vfio_pci.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
index 6968b72..d
Move the device reset to the end of our disable path, the device
should already be stopped from pci_disable_device(). This also allows
us to manipulate the save/restore to avoid the save/reset/restore +
save/restore that we had before.
Signed-off-by: Alex Williamson
---
Hannes, I think this doe
David-
Thanks for the followup. That is disappointing, and I wish I knew why the
performance is so poor. With the kernel and qemu replaced, I don't know
where the limitation is - raising the MTU makes no difference, and I also
tried a few different kernels inside the guest. The network stack ca
Thanks for your reply. As you agree there is an actual bug in this code, would
you kindly be able to tell me when a fix would be available in the Linux trunk?
Thanks and best regards, Melanie Blower
-Original Message-
From: H. Peter Anvin [mailto:h...@zytor.com]
Sent: Wednesday, November
On 11/15/2012 04:08 AM, Marcelo Tosatti wrote:
> As requested by Glauber, do not update kvmclock area on vcpu->pcpu
> migration, in case the host has stable TSC.
>
> This is to reduce cacheline bouncing.
>
> Signed-off-by: Marcelo Tosatti
This looks fine, but it can always get tricky...
Assumi
On 11/15/2012 04:08 AM, Marcelo Tosatti wrote:
> As noted by Gleb, not advertising SSE2 support implies
> no RDTSC barriers.
>
> Signed-off-by: Marcelo Tosatti
And this gets a separate patch because?
> Index: vsyscall/arch/x86/include/asm/pvclock.h
>
On 11/15/2012 04:08 AM, Marcelo Tosatti wrote:
> Signed-off-by: Marcelo Tosatti
>
>
> Index: vsyscall/arch/x86/kernel/pvclock.c
> ===
> --- vsyscall.orig/arch/x86/kernel/pvclock.c
Acked-by: Glauber Costa
--
To unsubscribe from thi
On 11/15/2012 04:08 AM, Marcelo Tosatti wrote:
> Originally from Jeremy Fitzhardinge.
>
> So code can be reused.
>
> Signed-off-by: Marcelo Tosatti
>
I thought I had acked this one already?
But maybe I didn't...
Acked-by: Glauber Costa
--
To unsubscribe from this list: send the line "unsubsc
Hi, everyone
I am studying KVM code.
And I try to intercept a guest's read access to a page using VMX and
EPT support.
According to Intel Manual, the lowest bit of the EPT page table entry
is used to
control read access to a page.
I modified the rmap_write_protect function to remove the
VMX_EPT
On 11/15/2012 04:08 AM, Marcelo Tosatti wrote:
> We want to expose the pvclock shared memory areas, which
> the hypervisor periodically updates, to userspace.
>
> For a linear mapping from userspace, it is necessary that
> entire page sized regions are used for array of pvclock
> structures.
>
25 matches
Mail list logo
