All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Jérémy Fanguède" <j.fanguede@virtualopensystems.com>,
	"Christoffer Dall" <christoffer.dall@linaro.org>
Cc: list@lists.cs.columbia.edu, Overall <kvm@vger.kernel.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	open@lists.cs.columbia.edu,
	VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl
Date: Thu, 07 May 2015 19:01:36 +0200	[thread overview]
Message-ID: <554B9A70.6020309@redhat.com> (raw)
In-Reply-To: <CAGE1QJoEAg9tAM63MEbpLuqvY_ZwGrHPU1sqo=L_iByKrERUow@mail.gmail.com>



On 07/05/2015 18:56, Jérémy Fanguède wrote:
> USB devices fail with a timeout error, as if the communication between
> the kernel and the devices fail at a certain point:
> usb 1-1: device not accepting address 5, error -110
> usb usb1-port1: unable to enumerate USB device
> 
> e1000 fails when the userspace tries to use it, with these type of
> kernel messages:
> e1000 0000:00:02.0 eth0: Detected Tx Unit Hang
>   Tx Queue             <0>
>   TDH                  <d>
>   TDT                  <d>
>   next_to_use          <d>
>   next_to_clean        <9>
> buffer_info[next_to_clean]
>   time_stamp           <ffff9311>
>   next_to_watch        <a>
>   jiffies              <ffff956a>
>   next_to_watch.status <0>

Can you find out what memory attributes the guest is using for the
memory---and if it's uncached, why?

Paolo
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

WARNING: multiple messages have this Message-ID (diff)
From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl
Date: Thu, 07 May 2015 19:01:36 +0200	[thread overview]
Message-ID: <554B9A70.6020309@redhat.com> (raw)
In-Reply-To: <CAGE1QJoEAg9tAM63MEbpLuqvY_ZwGrHPU1sqo=L_iByKrERUow@mail.gmail.com>



On 07/05/2015 18:56, J?r?my Fangu?de wrote:
> USB devices fail with a timeout error, as if the communication between
> the kernel and the devices fail at a certain point:
> usb 1-1: device not accepting address 5, error -110
> usb usb1-port1: unable to enumerate USB device
> 
> e1000 fails when the userspace tries to use it, with these type of
> kernel messages:
> e1000 0000:00:02.0 eth0: Detected Tx Unit Hang
>   Tx Queue             <0>
>   TDH                  <d>
>   TDT                  <d>
>   next_to_use          <d>
>   next_to_clean        <9>
> buffer_info[next_to_clean]
>   time_stamp           <ffff9311>
>   next_to_watch        <a>
>   jiffies              <ffff956a>
>   next_to_watch.status <0>

Can you find out what memory attributes the guest is using for the
memory---and if it's uncached, why?

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Jérémy Fanguède" <j.fanguede@virtualopensystems.com>,
	"Christoffer Dall" <christoffer.dall@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Overall <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl
Date: Thu, 07 May 2015 19:01:36 +0200	[thread overview]
Message-ID: <554B9A70.6020309@redhat.com> (raw)
In-Reply-To: <CAGE1QJoEAg9tAM63MEbpLuqvY_ZwGrHPU1sqo=L_iByKrERUow@mail.gmail.com>



On 07/05/2015 18:56, Jérémy Fanguède wrote:
> USB devices fail with a timeout error, as if the communication between
> the kernel and the devices fail at a certain point:
> usb 1-1: device not accepting address 5, error -110
> usb usb1-port1: unable to enumerate USB device
> 
> e1000 fails when the userspace tries to use it, with these type of
> kernel messages:
> e1000 0000:00:02.0 eth0: Detected Tx Unit Hang
>   Tx Queue             <0>
>   TDH                  <d>
>   TDT                  <d>
>   next_to_use          <d>
>   next_to_clean        <9>
> buffer_info[next_to_clean]
>   time_stamp           <ffff9311>
>   next_to_watch        <a>
>   jiffies              <ffff956a>
>   next_to_watch.status <0>

Can you find out what memory attributes the guest is using for the
memory---and if it's uncached, why?

Paolo

  reply	other threads:[~2015-05-07 16:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05  9:13 [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl Jérémy Fanguède
2015-05-05  9:13 ` [Qemu-devel] " Jérémy Fanguède
2015-05-05  9:13 ` Jérémy Fanguède
2015-05-06 14:12 ` Christoffer Dall
2015-05-06 14:12   ` [Qemu-devel] " Christoffer Dall
2015-05-06 14:12   ` Christoffer Dall
2015-05-07 10:50   ` Jérémy Fanguède
2015-05-07 10:50     ` [Qemu-devel] " Jérémy Fanguède
2015-05-07 10:50     ` Jérémy Fanguède
2015-05-07 11:20     ` Christoffer Dall
2015-05-07 11:20       ` [Qemu-devel] " Christoffer Dall
2015-05-07 11:20       ` Christoffer Dall
2015-05-07 14:50       ` Jérémy Fanguède
2015-05-07 14:50         ` [Qemu-devel] " Jérémy Fanguède
2015-05-07 14:50         ` Jérémy Fanguède
2015-05-07 15:34         ` Christoffer Dall
2015-05-07 15:34           ` [Qemu-devel] " Christoffer Dall
2015-05-07 15:34           ` Christoffer Dall
2015-05-07 16:56           ` Jérémy Fanguède
2015-05-07 16:56             ` [Qemu-devel] " Jérémy Fanguède
2015-05-07 16:56             ` Jérémy Fanguède
2015-05-07 17:01             ` Paolo Bonzini [this message]
2015-05-07 17:01               ` [Qemu-devel] " Paolo Bonzini
2015-05-07 17:01               ` Paolo Bonzini
2015-05-15 11:43               ` Laszlo Ersek
2015-05-15 11:43                 ` [Qemu-devel] " Laszlo Ersek
2015-05-15 11:43                 ` Laszlo Ersek
2015-05-15 15:12                 ` Christoffer Dall
2015-05-15 15:12                   ` [Qemu-devel] " Christoffer Dall
2015-05-15 15:12                   ` Christoffer Dall
2015-05-15 15:24                   ` Paolo Bonzini
2015-05-15 15:24                     ` [Qemu-devel] " Paolo Bonzini
2015-05-15 15:24                     ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=554B9A70.6020309@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=christoffer.dall@linaro.org \
    --cc=j.fanguede@virtualopensystems.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=list@lists.cs.columbia.edu \
    --cc=open@lists.cs.columbia.edu \
    --cc=qemu-devel@nongnu.org \
    --cc=tech@virtualopensystems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.