On 01/26/2011 08:31 AM, Jan Kiszka wrote:
On 2011-01-26 14:15, Jan Kiszka wrote:
On 2011-01-26 14:08, Stefan Berger wrote:
On 01/26/2011 07:09 AM, Jan Kiszka wrote:
On 2011-01-26 13:05, Stefan Berger wrote:
On 01/26/2011 03:14 AM, Jan Kiszka wrote:
On 2011-01-25 17:49, Stefan Berger wrote:
On 2011-01-26 14:15, Jan Kiszka wrote:
> On 2011-01-26 14:08, Stefan Berger wrote:
>> On 01/26/2011 07:09 AM, Jan Kiszka wrote:
>>> On 2011-01-26 13:05, Stefan Berger wrote:
On 01/26/2011 03:14 AM, Jan Kiszka wrote:
> On 2011-01-25 17:49, Stefan Berger wrote:
>> On 01/25/2011 02:26 AM,
On 2011-01-26 14:08, Stefan Berger wrote:
> On 01/26/2011 07:09 AM, Jan Kiszka wrote:
>> On 2011-01-26 13:05, Stefan Berger wrote:
>>> On 01/26/2011 03:14 AM, Jan Kiszka wrote:
On 2011-01-25 17:49, Stefan Berger wrote:
> On 01/25/2011 02:26 AM, Jan Kiszka wrote:
>> Do you see a chance
On 01/26/2011 07:09 AM, Jan Kiszka wrote:
On 2011-01-26 13:05, Stefan Berger wrote:
On 01/26/2011 03:14 AM, Jan Kiszka wrote:
On 2011-01-25 17:49, Stefan Berger wrote:
On 01/25/2011 02:26 AM, Jan Kiszka wrote:
Do you see a chance to look closer at the issue yourself? E.g.
instrument the kerne
On 2011-01-26 13:05, Stefan Berger wrote:
> On 01/26/2011 03:14 AM, Jan Kiszka wrote:
>> On 2011-01-25 17:49, Stefan Berger wrote:
>>> On 01/25/2011 02:26 AM, Jan Kiszka wrote:
Do you see a chance to look closer at the issue yourself? E.g.
instrument the kernel's irqchip models and dump t
On 01/26/2011 03:14 AM, Jan Kiszka wrote:
On 2011-01-25 17:49, Stefan Berger wrote:
On 01/25/2011 02:26 AM, Jan Kiszka wrote:
Do you see a chance to look closer at the issue yourself? E.g.
instrument the kernel's irqchip models and dump their states once your
guest is stuck?
The device runs on
On 2011-01-25 17:49, Stefan Berger wrote:
> On 01/25/2011 02:26 AM, Jan Kiszka wrote:
>>
>> Do you see a chance to look closer at the issue yourself? E.g.
>> instrument the kernel's irqchip models and dump their states once your
>> guest is stuck?
> The device runs on iRQ 3. So I applied this patch
On 01/25/2011 02:26 AM, Jan Kiszka wrote:
Do you see a chance to look closer at the issue yourself? E.g.
instrument the kernel's irqchip models and dump their states once your
guest is stuck?
The device runs on iRQ 3. So I applied this patch here.
diff --git a/arch/x86/kvm/i8259.c b/arch/x86/k
On 2011-01-25 04:13, Stefan Berger wrote:
> On 01/24/2011 05:34 PM, Jan Kiszka wrote:
>> On 2011-01-24 19:27, Stefan Berger wrote:
>>> On 01/18/2011 03:53 AM, Jan Kiszka wrote:
On 2011-01-18 04:03, Stefan Berger wrote:
> On 01/16/2011 09:43 AM, Avi Kivity wrote:
>> On 01/14/2011 09:27
On 01/24/2011 05:34 PM, Jan Kiszka wrote:
On 2011-01-24 19:27, Stefan Berger wrote:
On 01/18/2011 03:53 AM, Jan Kiszka wrote:
On 2011-01-18 04:03, Stefan Berger wrote:
On 01/16/2011 09:43 AM, Avi Kivity wrote:
On 01/14/2011 09:27 PM, Stefan Berger wrote:
Can you sprinkle some printfs() aroun
On 2011-01-24 19:27, Stefan Berger wrote:
> On 01/18/2011 03:53 AM, Jan Kiszka wrote:
>> On 2011-01-18 04:03, Stefan Berger wrote:
>>> On 01/16/2011 09:43 AM, Avi Kivity wrote:
On 01/14/2011 09:27 PM, Stefan Berger wrote:
>> Can you sprinkle some printfs() arount kvm_run (in qemu-kvm.c) to
On 01/18/2011 03:53 AM, Jan Kiszka wrote:
On 2011-01-18 04:03, Stefan Berger wrote:
On 01/16/2011 09:43 AM, Avi Kivity wrote:
On 01/14/2011 09:27 PM, Stefan Berger wrote:
Can you sprinkle some printfs() arount kvm_run (in qemu-kvm.c) to
verify this?
Here's what I did:
interrupt exit reques
On 2011-01-18 04:03, Stefan Berger wrote:
> On 01/16/2011 09:43 AM, Avi Kivity wrote:
>> On 01/14/2011 09:27 PM, Stefan Berger wrote:
>>>
Can you sprinkle some printfs() arount kvm_run (in qemu-kvm.c) to
verify this?
>>> Here's what I did:
>>>
>>>
>>> interrupt exit requested
>>
On 01/16/2011 09:43 AM, Avi Kivity wrote:
On 01/14/2011 09:27 PM, Stefan Berger wrote:
Can you sprinkle some printfs() arount kvm_run (in qemu-kvm.c) to
verify this?
Here's what I did:
interrupt exit requested
It appears from this you're using qemu.git. Please try qemu-kvm.git,
wher
On 01/14/2011 09:27 PM, Stefan Berger wrote:
Can you sprinkle some printfs() arount kvm_run (in qemu-kvm.c) to
verify this?
Here's what I did:
interrupt exit requested
It appears from this you're using qemu.git. Please try qemu-kvm.git,
where the code appears to be correct.
--
erro
On 01/13/2011 05:22 AM, Avi Kivity wrote:
On 01/11/2011 06:19 PM, Stefan Berger wrote:
What puzzles me is that the read operation may be run twice but
others don't.
Reads have split execution: kvm emulates the mmio instruction, notices
that it cannot satisfy the read request, exits to qem
On 01/11/2011 06:19 PM, Stefan Berger wrote:
Hi!
I am currently doing some long-term testing of a device model using
memory mapped IO (TPM TIS) and am seeing some strange errors when the
suspend occurs in the middle of a read operation in the Linux TPM TIS
device driver where the driver rea
Hi!
I am currently doing some long-term testing of a device model using
memory mapped IO (TPM TIS) and am seeing some strange errors when the
suspend occurs in the middle of a read operation in the Linux TPM TIS
device driver where the driver reads the result packet from the mmio
location.
18 matches
Mail list logo
