Hi Gleb,
On 09/03/2014 11:04 PM, Gleb Natapov wrote:
On Wed, Sep 03, 2014 at 09:42:30AM +0800, tangchen wrote:
Hi Gleb,
On 09/03/2014 12:00 AM, Gleb Natapov wrote:
..
+static void vcpu_reload_apic_access_page(struct kvm_vcpu *vcpu)
+{
+ /*
+* apic access page could be migrat
On Monday 08 September 2014 06:35 PM, Alexander Graf wrote:
>
>
> On 07.09.14 18:31, Madhavan Srinivasan wrote:
>> This patch adds kernel side support for software breakpoint.
>> Design is that, by using an illegal instruction, we trap to hypervisor
>> via Emulation Assistance interrupt, where we
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #19 from Marti Raudsepp ---
(In reply to Joel Schopp from comment #15)
> It's not clear to me which devices were being put in the same group.
Hi Joel, any updates on this? I posted my IOMMU groups in comment #17 in case
you missed it.
On Monday 08 September 2014 06:39 PM, Alexander Graf wrote:
>
>
> On 07.09.14 18:31, Madhavan Srinivasan wrote:
>> This patch extends the use of illegal instruction as software
>> breakpoint instruction across the ppc platform. Patch extends
>> booke program interrupt code to support software bre
On 9 September 2014 11:35, Marc Zyngier wrote:
> Hi Ard,
>
>
> On 2014-09-08 21:29, Ard Biesheuvel wrote:
>>
>> The ISS encoding for an exception from a Data Abort has a WnR
>> bit[6] that indicates whether the Data Abort was caused by a
>> read or a write instruction. While there are several fiel
Hi Ard,
On 2014-09-08 21:29, Ard Biesheuvel wrote:
The ISS encoding for an exception from a Data Abort has a WnR
bit[6] that indicates whether the Data Abort was caused by a
read or a write instruction. While there are several fields
in the encoding that are only valid if the ISV bit[24] is set,
On Mon, Sep 08, 2014 at 11:21:44PM +0100, Joel Schopp wrote:
> Add a one liner to identify the gic-400. It's gicv2 with optional MSI
> extensions.
>
> Cc: Christoffer Dall
> Signed-off-by: Joel Schopp
> ---
> virt/kvm/arm/vgic.c |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/vir
The ISS encoding for an exception from a Data Abort has a WnR
bit[6] that indicates whether the Data Abort was caused by a
read or a write instruction. While there are several fields
in the encoding that are only valid if the ISV bit[24] is set,
WnR is not one of them, so we can read it uncondition
On Mon, Sep 08, 2014 at 11:29:51PM +0800, Amos Kong wrote:
> On Wed, Aug 06, 2014 at 01:55:29PM +0530, Amit Shah wrote:
> > On (Wed) 06 Aug 2014 [16:05:41], Amos Kong wrote:
> > > On Wed, Aug 06, 2014 at 01:35:15AM +0800, Amos Kong wrote:
> > > > When we try to hot-remove a busy virtio-rng device f
[resending, as ARM email server seems to be in some mood]
On 09/09/14 11:27, Ard Biesheuvel wrote:
> The ISS encoding for an exception from a Data Abort has a WnR
> bit[6] that indicates whether the Data Abort was caused by a
> read or a write instruction. While there are several fields
> in the e
When we try to hot-remove a busy virtio-rng device from QEMU monitor,
the device can't be hot-removed. Because virtio-rng driver hangs at
wait_for_completion_killable().
This patch exits the waiting by completing have_data completion before
unregistering, resets data_avail to avoid the hwrng core
I have tried Freebsd10.0 64bit VM on the KVM Host running RHEL 6.4, processor
Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz.
The Freebsd VM hangs at the "booting... " prompt.
If I boot the host kernel with "nosmep", then Freebsd VM boots up fine. I know
Xeon V2 processors are having the smep featur
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #20 from Joel Schopp ---
What updates are you looking for? Joerg's fix is now upstream.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe k
On Tue, Sep 9, 2014 at 4:12 AM, Venkateswara Rao Nandigam
wrote:
> I have tried Freebsd10.0 64bit VM on the KVM Host running RHEL 6.4, processor
> Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz.
>
> The Freebsd VM hangs at the "booting... " prompt.
>
> If I boot the host kernel with "nosmep", then Fre
Hi Amit, Rusty
RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1127062
steps:
- Read random data by 'dd if=/dev/hwrng of=/dev/null' in guest
- check sysfs files in the same time, 'cat /sys/class/misc/hw_random/rng_*'
Result: cat process will get stuck, it will return if we kill dd process.
We
(Resend to fix the subject)
Hi Amit, Rusty
RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1127062
steps:
- Read random data by 'dd if=/dev/hwrng of=/dev/null' in guest
- check sysfs files in the same time, 'cat /sys/class/misc/hw_random/rng_*'
Result: cat process will get stuck, it will retur
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #21 from Marti Raudsepp ---
(In reply to Joel Schopp from comment #20)
> What updates are you looking for? Joerg's fix is now upstream.
Yes, but there's still the issue with southbridge component isolation. You
requested more informa
I haven't tried on bare metal, but have seen some other list, where in some one
tried on bare metal and that was running well, as their VM on KVM was still
failing.
-Original Message-
From: Nakajima, Jun [mailto:jun.nakaj...@intel.com]
Sent: Tuesday, September 09, 2014 8:37 PM
To: Venka
On Mon, Jul 21, 2014 at 04:14:24PM +0300, Gleb Natapov wrote:
> On Wed, Jul 09, 2014 at 04:12:53PM -0300, mtosa...@redhat.com wrote:
> > Reload remote vcpus MMU from GET_DIRTY_LOG codepath, before
> > deleting a pinned spte.
> >
> > Signed-off-by: Marcelo Tosatti
> >
> > ---
> > arch/x86/kvm/mm
On Tue, Jul 22, 2014 at 05:59:42AM +0800, Xiao Guangrong wrote:
>
> On Jul 10, 2014, at 3:12 AM, mtosa...@redhat.com wrote:
>
> > Skip pinned shadow pages when selecting pages to zap.
>
> It seems there is no way to prevent changing pinned spte on
> zap-all path?
Xiao,
The way would be to relo
On Tue, Jul 22, 2014 at 05:55:20AM +0800, Xiao Guangrong wrote:
>
> On Jul 10, 2014, at 3:12 AM, mtosa...@redhat.com wrote:
>
> > Reload remote vcpus MMU from GET_DIRTY_LOG codepath, before
> > deleting a pinned spte.
> >
> > Signed-off-by: Marcelo Tosatti
> >
> > ---
> > arch/x86/kvm/mmu.c |
It looks like when this was initially merged it got accidentally included
in the following section. I've just moved it back in the correct section
and re-numbered it as other ioctls have been added since.
Signed-off-by: Alex Bennée
diff --git a/Documentation/virtual/kvm/api.txt
b/Documentation/
Hi,
I'm preparing to add ARM KVM GDB support and I went to read the API
documentation and found it surprisingly mute on the subject ;-)
The first patch documents the "new" KVM_SET_GUEST_DEBUG ioctl based on
reviewing the code. I've included a long CC list of people who've
actually done the variou
In preparation for working on the ARM implementation I noticed the debug
interface was missing from the API document. I've pieced together the
expected behaviour from the code and commit messages written it up as
best I can.
Signed-off-by: Alex Bennée
diff --git a/Documentation/virtual/kvm/api.t
This patch extends the use of illegal instruction as software
breakpoint instruction across the ppc platform. Patch extends
booke program interrupt code to support software breakpoint.
Signed-off-by: Madhavan Srinivasan
---
Patch is only compile tested. Will really help if
someone can try it out
This patchset adds ppc64 server side support for software breakpoint
and extends the use of illegal instruction as software
breakpoint across ppc platform.
Patch 1, adds kernel side support for software breakpoint.
Design is that, by using an illegal instruction, we trap to
hypervisor via Emulatio
This patch adds kernel side support for software breakpoint.
Design is that, by using an illegal instruction, we trap to hypervisor
via Emulation Assistance interrupt, where we check for the illegal instruction
and accordingly we return to Host or Guest. Patch also adds support for
software breakpo
On 09/01/2014 03:52 AM, David Marchand wrote:
>>> What about upgrading QEMU and ivshmem-server while you have existing
>>> guests? You cannot restart ivshmem-server, and the new QEMU would have
>>> to talk to the old ivshmem-server.
>>
>> Version negotiation also helps avoid confusion if someone
On Tue, Sep 09, 2014 at 05:27:19PM +0100, Alex Bennée wrote:
> It looks like when this was initially merged it got accidentally included
> in the following section.
Whoops.
> I've just moved it back in the correct section
> and re-numbered it as other ioctls have been added since.
>
> Signed-off
On 09.09.14 19:07, Madhavan Srinivasan wrote:
> This patch adds kernel side support for software breakpoint.
> Design is that, by using an illegal instruction, we trap to hypervisor
> via Emulation Assistance interrupt, where we check for the illegal instruction
> and accordingly we return to Hos
On 09.09.14 19:07, Madhavan Srinivasan wrote:
> This patchset adds ppc64 server side support for software breakpoint
> and extends the use of illegal instruction as software
> breakpoint across ppc platform.
>
> Patch 1, adds kernel side support for software breakpoint.
> Design is that, by usin
Hi everyone,
I was wondering if anyone could answer my confusion here. I am using qemu-kvm
0.12.1 installed with centos-6.5. I would like to use large pages to back my
guest vm, so I did it as this: http://www.linux-kvm.org/page/UsingLargePages,
and added "-mem-path /hugetlbfs" in the command t
Hi Amos,
On (Tue) 09 Sep 2014 [19:14:02], Amos Kong wrote:
> When we try to hot-remove a busy virtio-rng device from QEMU monitor,
> the device can't be hot-removed. Because virtio-rng driver hangs at
> wait_for_completion_killable().
>
> This patch exits the waiting by completing have_data compl
On (Tue) 09 Sep 2014 [23:23:07], Amos Kong wrote:
> (Resend to fix the subject)
>
> Hi Amit, Rusty
>
> RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1127062
> steps:
> - Read random data by 'dd if=/dev/hwrng of=/dev/null' in guest
> - check sysfs files in the same time, 'cat /sys/class/misc/h
RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1121540
When we try to hot-unplugging a busy virtio-rng device, the device
can't be removed. And the reading process in guest gets stuck.
Those two patches fixed this issue by completing have_data completion
and preventing invalid reading.
Thanks
When we try to hot-remove a busy virtio-rng device from QEMU monitor,
the device can't be hot-removed. Because virtio-rng driver hangs at
wait_for_completion_killable().
This patch exits the waiting by completing have_data completion before
unregistering, resets data_avail to avoid the hwrng core
Before we really unregister the hwrng device, reading will get stuck if
the virtio device is reset. We should return error for reading when we
start to remove the device.
Signed-off-by: Amos Kong
Cc: sta...@vger.kernel.org
---
drivers/char/hw_random/virtio-rng.c | 5 +
1 file changed, 5 inse
On Wed, Sep 10, 2014 at 11:04:54AM +0530, Amit Shah wrote:
> Hi Amos,
>
> On (Tue) 09 Sep 2014 [19:14:02], Amos Kong wrote:
> > When we try to hot-remove a busy virtio-rng device from QEMU monitor,
> > the device can't be hot-removed. Because virtio-rng driver hangs at
> > wait_for_completion_kill
On Wed, Sep 10, 2014 at 11:22:12AM +0530, Amit Shah wrote:
> On (Tue) 09 Sep 2014 [23:23:07], Amos Kong wrote:
> > (Resend to fix the subject)
> >
> > Hi Amit, Rusty
> >
> > RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1127062
> > steps:
> > - Read random data by 'dd if=/dev/hwrng of=/dev/nu
On Mon, Sep 08, 2014 at 06:18:46PM +0200, Paolo Bonzini wrote:
> Il 08/09/2014 17:56, Matt Mullins ha scritto:
> >> > What host are you running?
> > What information do you want that I missed in my first email?
>
> What version of QEMU? Can you try the 12.04 qemu (which IIRC is 1.0) on
> top of t
40 matches
Mail list logo
