On 9/6/15 10:32 PM, Paolo Bonzini wrote:
On 05/09/2015 00:38, Wanpeng Li wrote:
@@ -1940,11 +1975,16 @@ void kvm_vcpu_block(struct kvm_vcpu *vcpu)
* arrives.
*/
if (kvm_vcpu_check_block(vcpu) < 0) {
+polled = true;
Fantastic, thanks!
-Nathan
On 09/06/15 16:52, Paul Mackerras wrote:
On Sun, Sep 06, 2015 at 12:47:12PM -0700, Nathan Whitehorn wrote:
Anything I can do to help move these along? It's a big performance
improvement for FreeBSD guests.
These patches are in Paolo's kvm-ppc-next branch and should
Fantastic, thanks!
-Nathan
On 09/06/15 16:52, Paul Mackerras wrote:
On Sun, Sep 06, 2015 at 12:47:12PM -0700, Nathan Whitehorn wrote:
Anything I can do to help move these along? It's a big performance
improvement for FreeBSD guests.
These patches are in Paolo's kvm-ppc-next branch and should
Anything I can do to help move these along? It's a big performance
improvement for FreeBSD guests.
-Nathan
On 07/27/15 10:31, Nathan Whitehorn wrote:
I've been running with these patches and a FreeBSD guest for a while
now and they work very well, providing big performance improvements in
Anything I can do to help move these along? It's a big performance
improvement for FreeBSD guests.
-Nathan
On 07/27/15 10:31, Nathan Whitehorn wrote:
I've been running with these patches and a FreeBSD guest for a while
now and they work very well, providing big performance improvements in
On Sun, Sep 06, 2015 at 12:47:12PM -0700, Nathan Whitehorn wrote:
> Anything I can do to help move these along? It's a big performance
> improvement for FreeBSD guests.
These patches are in Paolo's kvm-ppc-next branch and should go into
Linus' tree in the next couple of days.
Paul.
--
To
On Sun, Sep 06, 2015 at 12:47:12PM -0700, Nathan Whitehorn wrote:
> Anything I can do to help move these along? It's a big performance
> improvement for FreeBSD guests.
These patches are in Paolo's kvm-ppc-next branch and should go into
Linus' tree in the next couple of days.
Paul.
--
To
On 09/02/2015 07:31 PM, Igor Mammedov wrote:
On Wed, 2 Sep 2015 18:36:43 +0800
Xiao Guangrong wrote:
On 09/02/2015 05:58 PM, Igor Mammedov wrote:
On Fri, 14 Aug 2015 22:51:59 +0800
Xiao Guangrong wrote:
Introduce
On 09/04/2015 08:02 PM, Igor Mammedov wrote:
On Fri, 14 Aug 2015 22:52:00 +0800
Xiao Guangrong wrote:
NVDIMM reserves all the free range above 4G to do:
- Persistent Memory (PMEM) mapping
- implement NVDIMM ACPI device _DSM method
Signed-off-by: Xiao
On 09/05/2015 05:07 AM, Clemens Gruber wrote:
Fixes the following compiler warning, occuring with GCC 5.2.0:
arch/x86/kvm/mmu.c: In function ‘handle_mmio_page_fault_common’:
arch/x86/kvm/mmu.c:3332:9: warning: ‘leaf’ may be used uninitialized in
this
function [-Wmaybe-uninitialized]
while
This will allow up to DISK_MAX_PARTS (256) partitions, with for example
GPT in the guest. Otherwise, the partition scan code will only discover
the first 15 partitions.
Signed-off-by: Fam Zheng
---
drivers/block/virtio_blk.c | 1 +
1 file changed, 1 insertion(+)
diff --git
On 09/02/2015 07:42 PM, Igor Mammedov wrote:
On Wed, 2 Sep 2015 18:43:41 +0800
Xiao Guangrong wrote:
On 09/02/2015 06:06 PM, Igor Mammedov wrote:
On Fri, 14 Aug 2015 22:51:55 +0800
Xiao Guangrong wrote:
Only 512M is left
On 06/09/2015 15:35, Alexander Kuleshov wrote:
> The process_smi_save_seg_64() function called only in the
> process_smi_save_state_64() if the CONFIG_X86_64 is set. This
> patch adds #ifdef CONFIG_X86_64 around process_smi_save_seg_64()
> to prevent following warning message:
>
>
On 03/09/2015 16:07, Wanpeng Li wrote:
> v6 -> v7:
> * explicit signal (set a bool)
> * fix the tracepoint
>
> v5 -> v6:
> * fix wait_ns and poll_ns
>
> v4 -> v5:
> * set base case 10us and max poll time 500us
> * handle short/long halt, idea from David, many thanks David
>
> v3 ->
The process_smi_save_seg_64() function called only in the
process_smi_save_state_64() if the CONFIG_X86_64 is set. This
patch adds #ifdef CONFIG_X86_64 around process_smi_save_seg_64()
to prevent following warning message:
arch/x86/kvm/x86.c:5946:13: warning: ‘process_smi_save_seg_64’ defined but
On 05/09/2015 00:38, Wanpeng Li wrote:
>>
>> @@ -1940,11 +1975,16 @@ void kvm_vcpu_block(struct kvm_vcpu *vcpu)
>>* arrives.
>>*/
>> if (kvm_vcpu_check_block(vcpu) < 0) {
>> +polled = true;
>>
On 03/09/2015 16:07, Wanpeng Li wrote:
> Change halt_poll_ns into per-VCPU variable, seeded from module parameter,
> to allow greater flexibility.
>
> Signed-off-by: Wanpeng Li
> ---
> include/linux/kvm_host.h | 1 +
> virt/kvm/kvm_main.c | 5 +++--
> 2 files
https://bugzilla.kernel.org/show_bug.cgi?id=104091
Bug ID: 104091
Summary: [bisected] Starting a VM causes the host to halt and
create Machine Check Exceptions
Product: Virtualization
Version: unspecified
Kernel Version: 4.2
https://bugzilla.kernel.org/show_bug.cgi?id=104091
--- Comment #2 from Michael Long ---
Created attachment 186871
--> https://bugzilla.kernel.org/attachment.cgi?id=186871=edit
VM configuration of the VM that is still working
--
You are receiving this mail because:
You are
On 09/06/2015 06:03 PM, bugzilla-dae...@bugzilla.kernel.org wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=104091
Bug ID: 104091
Summary: [bisected] Starting a VM causes the host to halt and
create Machine Check Exceptions
Product:
https://bugzilla.kernel.org/show_bug.cgi?id=104091
--- Comment #1 from Michael Long ---
Created attachment 186861
--> https://bugzilla.kernel.org/attachment.cgi?id=186861=edit
VM configuration of the VM causing the freeze
--
You are receiving this mail because:
You are
On 09/06/2015 05:56 PM, Stefan Geißler wrote:
Hi all,
Is there reliable information about the number of lines of code in the kvm code
base?
I already counted virt/kvm from the
git://git.kernel.org/pub/scm/virt/kvm/kvm.git repository. But
~7000 LOC seems too little to me. Or is that
Hi all,
Is there reliable information about the number of lines of code in the
kvm code base?
I already counted virt/kvm from the
git://git.kernel.org/pub/scm/virt/kvm/kvm.git repository. But ~7000 LOC
seems too little to me. Or is that correct?
Thank you in advance!
--
To unsubscribe
23 matches
Mail list logo