On Sun, Jan 8, 2012 at 3:26 AM, Takuya Yoshikawa
wrote:
> Hi,
>
> Nadav Amit wrote:
>> On Jan 7, 2012, at 10:25 PM, H. Peter Anvin wrote:
>>
>> > On 01/07/2012 12:21 PM, Nadav Amit wrote:
>> >> MOV immediate instruction (opcodes 0xB8-0xBF) may take 64-bit operand.
>> >> The previous emulation imp
On 01/07/2012 12:26 PM, Stefan Hajnoczi wrote:
> An Ubuntu 9.10 Karmic Koala guest is unable to boot or install due to
> missing movdqa emulation:
>
> kvm_exit: reason EXCEPTION_NMI rip 0x7fef3e025a7b info 7fef3e799000 8b0e
> kvm_page_fault: address 7fef3e799000 error_code f
> kvm_emulate_insn:
Linus, please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/3.3
to receive the KVM updates for the 3.3 cycle. Changes include a virtual
PMU available for guests, an MMU/MMIO speedup, more cpuid feature
whitelisting, and cleanups.
The branch contains tip/perf, which you'v
On 01/05/2012 06:07 AM, Alexander Graf wrote:
> >
> > Hrm. Interesting idea. So you would basically reduce everything to __u64 by
> > padding smaller registers and splitting bigger ones into separate IDs? That
> > really is appealing, but might uglify the code quite a bit when remerging
> > big
On 01/04/2012 03:10 AM, Alexander Graf wrote:
> From: Scott Wood
>
> This implements a shared-memory API for giving host userspace access to
> the guest's TLB.
>
>
> +4.59 KVM_DIRTY_TLB
> +
> +Capability: KVM_CAP_SW_TLB
> +Architectures: ppc
> +Type: vcpu ioctl
> +Parameters: struct kvm_dirty_tl
On 01/04/2012 03:10 AM, Alexander Graf wrote:
> From: Scott Wood
>
> The hardcoded behavior prevents proper SMP support.
>
> QEMU shall specify the vcpu's PIR as the vcpu id.
s/QEMU/userspace/
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send
On 01/04/2012 03:10 AM, Alexander Graf wrote:
> With hugetlbfs support emerging on e500, we should also support KVM
> backing its guest memory by it.
>
> This patch adds support for hugetlbfs into the e500 shadow mmu code.
>
> Signed-off-by: Alexander Graf
> Acked-by: Scott Wood
>
> ---
>
> v1 ->
On 01/04/2012 03:10 AM, Alexander Graf wrote:
> From: Scott Wood
>
> Currently we check prior to returning from a lightweight exit,
> but not prior to initial entry.
>
> book3s already does a similar test.
>
> Signed-off-by: Scott Wood
> Signed-off-by: Alexander Graf
> ---
> arch/powerpc/kvm/bo
On 01/04/2012 03:10 AM, Alexander Graf wrote:
> From: Scott Wood
>
> This allows additional registers to be accessed by the guest
> in PR-mode KVM without trapping.
>
> SPRG4-7 are readable from userspace. On booke, KVM will sync
> these registers when it enters the guest, so that accesses from
>
On 01/04/2012 03:10 AM, Alexander Graf wrote:
> Our vcpu kick implementation differs a bit from x86 which resulted in us not
> disabling preemption during the kick. Get it a bit closer to what x86 does.
>
> Signed-off-by: Alexander Graf
> ---
> arch/powerpc/kvm/powerpc.c |7 ++-
> 1 files
On 01/04/2012 03:10 AM, Alexander Graf wrote:
> From: Paul Mackerras
>
> This adds the infrastructure to enable us to page out pages underneath
> a Book3S HV guest, on processors that support virtualized partition
> memory, that is, POWER7. Instead of pinning all the guest's pages,
> we now look
Check how long it takes to get dirty log according to the number of
dirty pages, like:
get dirty log: 49 us for 1 dirty pages
get dirty log: 49 us for 2 dirty pages
get dirty log: 45 us for 4 dirty pages
get dirty log: 41 us for 8 dirty p
On 01/08/2012 10:47 AM, Nadav Amit wrote:
> On Sun, Jan 8, 2012 at 3:26 AM, Takuya Yoshikawa
> wrote:
> > Hi,
> >
> > Nadav Amit wrote:
> >> On Jan 7, 2012, at 10:25 PM, H. Peter Anvin wrote:
> >>
> >> > On 01/07/2012 12:21 PM, Nadav Amit wrote:
> >> >> MOV immediate instruction (opcodes 0xB8-0xB
On 01/08/2012 04:05 PM, Avi Kivity wrote:
> >
> > Avi, please acknowledge adding OpImm64.
>
> Yes, OpImm64 is the cleanest IMO. Note it doesn't even cost us a bit.
Note, usually I'd ask for a unit test to accompany the fix, but the
current framework only supports testing instructions that have a
On 01/08/2012 03:58 PM, Takuya Yoshikawa wrote:
> Check how long it takes to get dirty log according to the number of
> dirty pages, like:
>
> get dirty log: 49 us for 1 dirty pages
> get dirty log: 49 us for 2 dirty pages
> get dirty log: 45 us for 4 di
On Sun, Jan 8, 2012 at 4:08 PM, Avi Kivity wrote:
> On 01/08/2012 04:05 PM, Avi Kivity wrote:
>> >
>> > Avi, please acknowledge adding OpImm64.
>>
>> Yes, OpImm64 is the cleanest IMO. Note it doesn't even cost us a bit.
Very well - I'll submit a revised patch later.
>
> Note, usually I'd ask fo
On Sun, 08 Jan 2012 16:21:08 +0200
Avi Kivity wrote:
> On 01/08/2012 03:58 PM, Takuya Yoshikawa wrote:
> > Check how long it takes to get dirty log according to the number of
> > dirty pages, like:
> >
> > get dirty log: 49 us for 1 dirty pages
> > get dirty log: 49 us for
On 01/07/2012 12:37 PM, Stefan Hajnoczi wrote:
> The unimplemented movdqa (66 0f 7f 07) instruction triggers a bug in
> the x86 emulator. The emulator should fail since the instruction is
> unimplemented. However the emulator thinks it is succeeding but we
> keep re-executing the same instructio
On 08.01.2012, at 14:13, Avi Kivity wrote:
> On 01/04/2012 03:10 AM, Alexander Graf wrote:
>> From: Scott Wood
>>
>> This implements a shared-memory API for giving host userspace access to
>> the guest's TLB.
>>
>>
>> +4.59 KVM_DIRTY_TLB
>> +
>> +Capability: KVM_CAP_SW_TLB
>> +Architectures:
On 08.01.2012, at 14:14, Avi Kivity wrote:
> On 01/04/2012 03:10 AM, Alexander Graf wrote:
>> From: Scott Wood
>>
>> The hardcoded behavior prevents proper SMP support.
>>
>> QEMU shall specify the vcpu's PIR as the vcpu id.
>
> s/QEMU/userspace/
This is a pull request, not a review request.
On 01/08/2012 04:49 PM, Takuya Yoshikawa wrote:
> > > +
> > > +gettimeofday(&start_time, NULL);
> > > +slot.update_dirty_log();
> > > +gettimeofday(&end_time, NULL);
> >
> > Nicer to have a function that returns time in nanoseconds.
>
> I don't know such an API which can be
On 01/08/2012 04:52 PM, Alexander Graf wrote:
> On 08.01.2012, at 14:13, Avi Kivity wrote:
>
> > On 01/04/2012 03:10 AM, Alexander Graf wrote:
> >> From: Scott Wood
> >>
> >> This implements a shared-memory API for giving host userspace access to
> >> the guest's TLB.
> >>
> >>
> >> +4.59 KVM_D
On 01/08/2012 04:53 PM, Alexander Graf wrote:
> On 08.01.2012, at 14:14, Avi Kivity wrote:
>
> > On 01/04/2012 03:10 AM, Alexander Graf wrote:
> >> From: Scott Wood
> >>
> >> The hardcoded behavior prevents proper SMP support.
> >>
> >> QEMU shall specify the vcpu's PIR as the vcpu id.
> >
> >
Here is the corresponding kvm-kmod [1] release for Linux 3.2. The
package is available for download from
http://sourceforge.net/projects/kvm/files/kvm-kmod/3.2/kvm-kmod-3.2.tar.bz2/download
Major KVM changes since kvm-kmod-3.1:
- APIC: Optimize EOI emulation
- APIC: Emulate TSC deadline timer
On 08.01.2012, at 14:18, Avi Kivity wrote:
> On 01/04/2012 03:10 AM, Alexander Graf wrote:
>> From: Scott Wood
>>
>> Currently we check prior to returning from a lightweight exit,
>> but not prior to initial entry.
>>
>> book3s already does a similar test.
>>
>> Signed-off-by: Scott Wood
>>
On 08.01.2012, at 14:24, Avi Kivity wrote:
> On 01/04/2012 03:10 AM, Alexander Graf wrote:
>> Our vcpu kick implementation differs a bit from x86 which resulted in us not
>> disabling preemption during the kick. Get it a bit closer to what x86 does.
>>
>> Signed-off-by: Alexander Graf
>> ---
>>
On 08.01.2012, at 14:29, Avi Kivity wrote:
> On 01/04/2012 03:10 AM, Alexander Graf wrote:
>> From: Paul Mackerras
>>
>> This adds the infrastructure to enable us to page out pages underneath
>> a Book3S HV guest, on processors that support virtualized partition
>> memory, that is, POWER7. Ins
On 08.01.2012, at 15:55, Avi Kivity wrote:
> On 01/08/2012 04:52 PM, Alexander Graf wrote:
>> On 08.01.2012, at 14:13, Avi Kivity wrote:
>>
>>> On 01/04/2012 03:10 AM, Alexander Graf wrote:
From: Scott Wood
This implements a shared-memory API for giving host userspace access to
On 01/08/2012 05:11 PM, Alexander Graf wrote:
> On 08.01.2012, at 14:18, Avi Kivity wrote:
>
> > On 01/04/2012 03:10 AM, Alexander Graf wrote:
> >> From: Scott Wood
> >>
> >> Currently we check prior to returning from a lightweight exit,
> >> but not prior to initial entry.
> >>
> >> book3s alre
On 01/08/2012 05:15 PM, Alexander Graf wrote:
> On 08.01.2012, at 14:29, Avi Kivity wrote:
>
> > On 01/04/2012 03:10 AM, Alexander Graf wrote:
> >> From: Paul Mackerras
> >>
> >> This adds the infrastructure to enable us to page out pages underneath
> >> a Book3S HV guest, on processors that supp
On 01/08/2012 05:16 PM, Alexander Graf wrote:
> >
> > Okay - I guess it's different to x86. And I think we had this
> > conversation before...
>
> In fact, this is the 3rd time I remember having this discussion on exactly
> this patch :).
Well it's only the first time this year, so it isn't so
On Jan 8, 2012, at 7:14 AM, Alexander Graf wrote:
>
> On 08.01.2012, at 14:24, Avi Kivity wrote:
>
>> On 01/04/2012 03:10 AM, Alexander Graf wrote:
>>> Our vcpu kick implementation differs a bit from x86 which resulted in us not
>>> disabling preemption during the kick. Get it a bit closer to w
On 08.01.2012, at 16:22, Avi Kivity wrote:
> On 01/08/2012 05:11 PM, Alexander Graf wrote:
>> On 08.01.2012, at 14:18, Avi Kivity wrote:
>>
>>> On 01/04/2012 03:10 AM, Alexander Graf wrote:
From: Scott Wood
Currently we check prior to returning from a lightweight exit,
but
On 08.01.2012, at 16:24, Avi Kivity wrote:
> On 01/08/2012 05:15 PM, Alexander Graf wrote:
>> On 08.01.2012, at 14:29, Avi Kivity wrote:
>>
>>> On 01/04/2012 03:10 AM, Alexander Graf wrote:
From: Paul Mackerras
This adds the infrastructure to enable us to page out pages undernea
On 01/08/2012 05:37 PM, Alexander Graf wrote:
> On 08.01.2012, at 16:22, Avi Kivity wrote:
>
> > On 01/08/2012 05:11 PM, Alexander Graf wrote:
> >> On 08.01.2012, at 14:18, Avi Kivity wrote:
> >>
> >>> On 01/04/2012 03:10 AM, Alexander Graf wrote:
> From: Scott Wood
>
> Currently
On 08.01.2012, at 17:13, Avi Kivity wrote:
> On 01/08/2012 05:37 PM, Alexander Graf wrote:
>> On 08.01.2012, at 16:22, Avi Kivity wrote:
>>
>>> On 01/08/2012 05:11 PM, Alexander Graf wrote:
On 08.01.2012, at 14:18, Avi Kivity wrote:
> On 01/04/2012 03:10 AM, Alexander Graf wrote:
On Sun, Jan 8, 2012 at 10:32 AM, Avi Kivity wrote:
> On 01/07/2012 12:26 PM, Stefan Hajnoczi wrote:
>>
>> movdqa %xmm0,(%rdi)
>>
>> This patch adds movdqa to the emulator but does not implement #GP when
>> the memory operand is unaligned to 16 bytes. I'm not sure whether
>> alignment checking can
On 01/08/2012 06:21 PM, Alexander Graf wrote:
> >
> > well, that's not actually what x86 does, but what it should be doing.
> > The point is checking for signals after an exit is meaningless. You've
> > exited, so the guest can't be holding off a signal for the host. The
> > check after the exi
On Sun, Jan 08, 2012 at 04:21:56PM +, Stefan Hajnoczi wrote:
> On Sun, Jan 8, 2012 at 10:32 AM, Avi Kivity wrote:
> > On 01/07/2012 12:26 PM, Stefan Hajnoczi wrote:
> >>
> >> movdqa %xmm0,(%rdi)
> >>
> >> This patch adds movdqa to the emulator but does not implement #GP when
> >> the memory op
On 01/08/2012 06:21 PM, Stefan Hajnoczi wrote:
> On Sun, Jan 8, 2012 at 10:32 AM, Avi Kivity wrote:
> > On 01/07/2012 12:26 PM, Stefan Hajnoczi wrote:
> >>
> >> movdqa %xmm0,(%rdi)
> >>
> >> This patch adds movdqa to the emulator but does not implement #GP when
> >> the memory operand is unaligned
On 08.01.2012, at 17:26, Avi Kivity wrote:
> On 01/08/2012 06:21 PM, Alexander Graf wrote:
>>>
>>> well, that's not actually what x86 does, but what it should be doing.
>>> The point is checking for signals after an exit is meaningless. You've
>>> exited, so the guest can't be holding off a si
On 01/08/2012 06:41 PM, Alexander Graf wrote:
> On 08.01.2012, at 17:26, Avi Kivity wrote:
>
> > On 01/08/2012 06:21 PM, Alexander Graf wrote:
> >>>
> >>> well, that's not actually what x86 does, but what it should be doing.
> >>> The point is checking for signals after an exit is meaningless. Y
Am 07.01.2012 18:52, schrieb Binarus:
> - Is it possible to run a guest with a mixture of I/O virtualization
> technologies, i.e. run the most part of the guest by using KVM with VT-d and
> VT-x, but "emulate" the PCI device without using these technologies?
Yes, graphics card, network card, etc
On 08.01.2012, at 17:45, Avi Kivity wrote:
> On 01/08/2012 06:41 PM, Alexander Graf wrote:
>> On 08.01.2012, at 17:26, Avi Kivity wrote:
>>
>>> On 01/08/2012 06:21 PM, Alexander Graf wrote:
>
> well, that's not actually what x86 does, but what it should be doing.
> The point is che
On 2012-01-07 19:23, Liu, Jinsong wrote:
> Jan Kiszka wrote:
>> On 2012-01-05 18:07, Liu, Jinsong wrote:
Sorry, it remains bogus to expose the tsc deadline timer feature on
machines < pc-1.1. That's just like we introduced kvmclock only to
pc-0.14 onward. The reason is that guest OSe
On Tue, 19 Jul 2011, Hannes Reinecke wrote:
This patch adds an emulation for the LSI Megaraid SAS 8708EM2 HBA.
It is based off the 'block' tree from Kevin Wolf, as he pulled
in the preliminary patches.
I've tested it to work with Linux, Windows Vista, and Windows7.
Why hasn't this patch already
During creation of the pc-0.15 machine type something must have gone wrong
and the is_default field was still set, even though our default machine is
1.0. Remove that field.
Signed-off-by: Alexander Graf
diff --git a/hw/pc_piix.c b/hw/pc_piix.c
index b70431f..00f525e 100644
--- a/hw/pc_piix.c
++
When running QEMU without -cpu parameter, the user usually wants a sane
default. So far, we're using the qemu64/qemu32 CPU type, which basically
means "the maximum TCG can emulate".
That's a really good default when using TCG, but when running with KVM
we much rather want a default saying "the max
During discussions on whether to make -cpu host the default in SLE, I found
myself disagreeing to the thought, because it potentially opens a big can
of worms for potential bugs. But if I already am so opposed to it for SLE, how
can it possibly be reasonable to default to -cpu host in upstream QEMU
On 09.01.2012, at 00:52, Alexander Graf wrote:
> During creation of the pc-0.15 machine type something must have gone wrong
> and the is_default field was still set, even though our default machine is
> 1.0. Remove that field.
>
> Signed-off-by: Alexander Graf
Oops, sorry. Misused git-send-mai
On 8 January 2012 23:52, Alexander Graf wrote:
> During discussions on whether to make -cpu host the default in SLE, I found
> myself disagreeing to the thought, because it potentially opens a big can
> of worms for potential bugs. But if I already am so opposed to it for SLE, how
> can it possibl
On 09.01.2012, at 01:02, Peter Maydell wrote:
> On 8 January 2012 23:52, Alexander Graf wrote:
>> During discussions on whether to make -cpu host the default in SLE, I found
>> myself disagreeing to the thought, because it potentially opens a big can
>> of worms for potential bugs. But if I alre
Am 08.01.2012 22:56, schrieb Gerhard Wiesinger:
> On Tue, 19 Jul 2011, Hannes Reinecke wrote:
>> This patch adds an emulation for the LSI Megaraid SAS 8708EM2 HBA.
>> It is based off the 'block' tree from Kevin Wolf, as he pulled
>> in the preliminary patches.
>> I've tested it to work with Linux,
On 12/16/2011 06:13 PM, Xiao Guangrong wrote:
> In this patchset, we observably reduce the size of struct kvm_mmu_page and let
> the code more simple.
>
> And this patchset have already tested by unittest and
> RHEL.6.1 setup/boot/reboot/shutdown.
Hi Avi, Marcelo,
Could you please apply patch
This commit adds a target for 'lkvm-static' which is linked -static.
(This can be useful to construct kvmtool binaries for minimalist
auto-test host filesystems.)
Signed-off-by: Matt Evans
---
Pekka, I found this useful in one of our test setups, hopefully
others will too.
Cheers, Matt
too
On 01/07/2012 02:21 PM, Gordon Messmer wrote:
I'm certain that qemu-kvm loads both
/usr/share/qemu-kvm/vgabios-cirrus.bin and
/var/lib/libvirt/images/Radeon3470.rom, which seems correct. However,
in the guest, both the virtual VGA card and the real PCI one have the
same ROM, from vgabios-cirrus.
This commit adds a target for 'lkvm-static' which is linked -static.
(This can be useful to construct kvmtool binaries for minimalist
auto-test host filesystems.)
Signed-off-by: Matt Evans
---
V2: Argh! Let's remove it on make clean, too...
tools/kvm/Makefile |6 +-
1 files changed,
On Mon, 9 Jan 2012, Matt Evans wrote:
This commit adds a target for 'lkvm-static' which is linked -static.
(This can be useful to construct kvmtool binaries for minimalist
auto-test host filesystems.)
Signed-off-by: Matt Evans
I'm fine with this. Ingo, Sasha?
---
V2: Argh! Let's remove
> -Original Message-
> From: Jan Kiszka [mailto:jan.kis...@web.de]
> Sent: Saturday, January 07, 2012 1:27 AM
> However, not having looked at details yet, two things jumped at me:
> - You cannot simply change the vmstate format without caring about
>migration from older qemu versions.
hi~
I noticed that there is no configuration for RHEL6.2 in
/client/virt/guest-os.cfg.sample.
Here is the patch.
Please comment!:)
Signed-off-by: tangchen
---
client/virt/guest-os.cfg.sample | 36
1 files changed, 36 insertions(+), 0 deletions(-)
diff -
On 01/09/2012 02:45 PM, Matt Evans wrote:
> This commit adds a target for 'lkvm-static' which is linked -static.
>
> (This can be useful to construct kvmtool binaries for minimalist
> auto-test host filesystems.)
This is useful. However, It fails to build for me. Some problem with
sdl, bfd and vn
61 matches
Mail list logo
