On 07/23/2015 02:26 PM, Paolo Bonzini wrote:
Make them clearly architecture-dependent; the capability is valid for
all architectures, but the argument is not.
Reviewed-by: Xiao Guangrong
Okay, i saw you already have adjusted and merged my patchset, thanks for your
work. :)
--
To unsubscrib
On 07/23/2015 02:21 PM, Paolo Bonzini wrote:
On 16/07/2015 06:10, Alex Williamson wrote:
On Thu, 2015-07-16 at 03:25 +0800, Xiao Guangrong wrote:
From: Xiao Guangrong
Currently code uses default memory type if MTRR is fully disabled,
fix it by using UC instead
Signed-off-by: Xiao Guangro
Make them clearly architecture-dependent; the capability is valid for
all architectures, but the argument is not.
Signed-off-by: Paolo Bonzini
---
arch/x86/include/uapi/asm/kvm.h | 4 ++--
arch/x86/kvm/lapic.c| 2 +-
arch/x86/kvm/svm.c | 2 +-
arch/x86/kvm/vmx.c
On 16/07/2015 06:10, Alex Williamson wrote:
> On Thu, 2015-07-16 at 03:25 +0800, Xiao Guangrong wrote:
>> > From: Xiao Guangrong
>> >
>> > Currently code uses default memory type if MTRR is fully disabled,
>> > fix it by using UC instead
>> >
>> > Signed-off-by: Xiao Guangrong
>> > ---
> Seem
On 07/23/2015 01:56 PM, Paolo Bonzini wrote:
On 15/07/2015 21:25, Xiao Guangrong wrote:
From: Xiao Guangrong
Current firmware depends on WB to fast boot, please refer to
https://lkml.org/lkml/2015/7/12/115
Let's us WB if CR0.CD is set to make this kind of firmware happy
This quirk
On 15/07/2015 21:25, Xiao Guangrong wrote:
> From: Xiao Guangrong
>
> Current firmware depends on WB to fast boot, please refer to
> https://lkml.org/lkml/2015/7/12/115
>
> Let's us WB if CR0.CD is set to make this kind of firmware happy
>
> This quirk can be dropped by using KVM_ENABLE
On Wed, 22 Jul 2015, Vlastimil Babka wrote:
> > alloc_pages_exact_node(), as you said, connotates that the allocation will
> > take place on that node or will fail. So why not go beyond this patch and
> > actually make alloc_pages_exact_node() set __GFP_THISNODE and then call
> > into a new alloc
On Wed, 22 Jul 2015, Paolo Bonzini wrote:
> > diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> > index 2d73807..a8723a8 100644
> > --- a/arch/x86/kvm/vmx.c
> > +++ b/arch/x86/kvm/vmx.c
> > @@ -3158,7 +3158,7 @@ static struct vmcs *alloc_vmcs_cpu(int cpu)
> > struct page *pages;
> > s
Ozgur O Kilic writes:
> Hi,
>
> I was trying to find out the max number of vpcus and what is the
> reason of having that. I found 2 number about it one is the recommend
> max by KVM which is 160 and the other number was 255. Can someone
> tell me what are the reasons of this limitations? Why 160
Hi,
I was trying to find out the max number of vpcus and what is the
reason of having that. I found 2 number about it one is the recommend
max by KVM which is 160 and the other number was 255. Can someone
tell me what are the reasons of this limitations? Why 160 is the
recommended max and why the
This is useful information for the run scripts to know, especially if
they want to drop to using TCG.
Signed-off-by: Alex Bennée
Reviewed-by: Andrew Jones
---
v3
- add r-b tag
---
configure | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configure b/configure
index b2ad32a..078b70c 100
One minor fix for quote usage and added a final r-b tag from Drew.
Please apply
Alex Bennée (3):
README: add some CONTRIBUTING notes
configure: emit HOST=$host to config.mak
arm/run: introduce usingkvm var and use it
README| 26 ++
arm/run | 18 ++
This makes the script a little cleaner by only checking for KVM support
in one place. If KVM isn't available we can fall back to TCG emulation
and echo the fact to the screen rather than let QEMU complain.
Signed-off-by: Alex Bennée
Reviewed-by: Andrew Jones
---
v2
- rm redundant M= statement
Signed-off-by: Alex Bennée
Reviewed-by: Andrew Jones
---
v2
- mention consistency
v3
- add r-b tag
---
README | 26 ++
1 file changed, 26 insertions(+)
diff --git a/README b/README
index e9869d1..9389a26 100644
--- a/README
+++ b/README
@@ -25,3 +25,29 @@ Directory
On Wed, 2015-07-22 at 10:54 -0600, Alex Williamson wrote:
> On Tue, 2015-07-21 at 19:44 +0200, Gerald Schaefer wrote:
> > When a user completes the VFIO_SET_IOMMU ioctl and the vfio-pci device is
> > removed thereafter (before any other ioctl like VFIO_GROUP_GET_DEVICE_FD),
> > then the detach_dev
On Tue, 2015-07-21 at 19:44 +0200, Gerald Schaefer wrote:
> When a user completes the VFIO_SET_IOMMU ioctl and the vfio-pci device is
> removed thereafter (before any other ioctl like VFIO_GROUP_GET_DEVICE_FD),
> then the detach_dev callback of the underlying IOMMU API is never called.
>
> This pa
On 07/21/2015 11:31 PM, David Rientjes wrote:
> On Tue, 21 Jul 2015, Vlastimil Babka wrote:
>
>> The function alloc_pages_exact_node() was introduced in 6484eb3e2a81 ("page
>> allocator: do not check NUMA node ID when the caller knows the node is
>> valid")
>> as an optimized variant of alloc_pag
On 21/07/2015 15:55, Vlastimil Babka wrote:
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index 2d73807..a8723a8 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -3158,7 +3158,7 @@ static struct vmcs *alloc_vmcs_cpu(int cpu)
> struct page *pages;
> struct v
Hello!
> It means that a pause in the discussion for a week (or even more) is not
> uncommon at all. It just means that the other party is busy with things
> of higher priority. In all cases, a gentle "ping" will be better
> received than this "you've stopped replying so I'm going to repost until
19 matches
Mail list logo
