xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Xu, YongweiX" <yongweix.xu@intel.com>
Cc: Jan Beulich <JBeulich@suse.com>,
	Sander Eikelenboom <linux@eikelenboom.it>,
	"Zhou, Chao" <chao.zhou@intel.com>,
	Joby Poriyath <joby.poriyath@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	"Liu, SongtaoX" <songtaox.liu@intel.com>
Subject: Re: [PATCH v8] interrupts: allow guest to set/clear MSI-X mask bit
Date: Mon, 16 Sep 2013 12:31:13 +0100	[thread overview]
Message-ID: <5236EC01.6040209@citrix.com> (raw)
In-Reply-To: <EE92950F97EE42469CA4F508D4691F5E01741E74@SHSMSX104.ccr.corp.intel.com>

On 16/09/2013 12:23, Xu, YongweiX wrote:
>> -----Original Message-----
>> From: Jan Beulich [mailto:JBeulich@suse.com]
>> Sent: Monday, September 16, 2013 5:37 PM
>> To: Joby Poriyath; Xu, YongweiX
>> Cc: Sander Eikelenboom; xen-devel
>> Subject: RE: [Xen-devel] [PATCH v8] interrupts: allow guest to set/clear MSI-X
>> mask bit
>>
>>>>> On 16.09.13 at 10:33, "Xu, YongweiX" <yongweix.xu@intel.com> wrote:
>>> I found your patch (Xen C/S:27480 7843bc3502ae) introduced a new
>>> issue, when I boot up a rhel6.4 guest with assigned a e1000e/igb/ixgbe
>>> PF or VF and more than 1 vcpu, the guest's network will be broken in a
>>> short time and cannot be recovered.
>>> The test machine was SandyBridge-EP and IvyTown-EP.
>> I would be very helpful if you could give some more detail: What specifically
>> doesn't work, logs, ...
>>
>> That's particularly important since, if indeed broken, the patch would need to
>> be reverted from at least the stable trees.
>>
>> Jan
> I've made further test about this issue, the config file as the attachment:rhel6u4.hvm(with qemu-xen), the result as below:
> 1. Boot up rhel6.4 guest with igbvf/ixgbevf/igbpf/ixgbepf/e1000e nic and 1 vcpu, the guest network works fine.
> 2. Boot up rhel6.4 guest with igbvf/ixgbevf/igbpf/ixgbepf/e1000e nic and 2(or more) vcpus, the guest can get IP first, but after about 10~20 seconds, the network will be broken.
> We can see only boot guest with more than 1 vcpu would cause this issue.
>
> Only when boot guest with e1000e nic and 2(2 or more)vcpus it would print call trace log, but I think it's enough to explain that the network broken caused by MSI-X, as the attachment:guest_with_e1000e.log.

And does reverting that specific changeset fix the issue?

I ask, because that change set specifically fixes SRIOV passthrough for
HVM guests using the ixgbevf driver, which was broken by an earlier
security enhancement.

~Andrew

  reply	other threads:[~2013-09-16 11:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 18:07 [PATCH v8] interrupts: allow guest to set/clear MSI-X mask bit Joby Poriyath
2013-09-05  8:02 ` Jan Beulich
2013-09-05  9:40   ` Joby Poriyath
2013-09-10 15:08     ` Sander Eikelenboom
2013-09-11 10:40       ` Joby Poriyath
2013-09-16  8:33         ` Xu, YongweiX
2013-09-16  9:36           ` Jan Beulich
2013-09-16 11:23             ` Xu, YongweiX
2013-09-16 11:31               ` Andrew Cooper [this message]
2013-09-17  4:50                 ` Xu, YongweiX
2013-09-16 11:51               ` Jan Beulich
2013-09-17  3:06                 ` Xu, YongweiX
2013-09-17  6:38                   ` Jan Beulich
2013-09-18  3:19                     ` Xu, YongweiX
2013-09-18  9:32                       ` Jan Beulich
2013-09-22  3:22                         ` Xu, YongweiX
2013-09-23  6:56                           ` Jan Beulich
2013-09-18 13:41                       ` Joby Poriyath
2013-09-22  2:07                         ` Xu, YongweiX

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=5236EC01.6040209@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=chao.zhou@intel.com \
    --cc=joby.poriyath@citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=songtaox.liu@intel.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=yongweix.xu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).