From: Juergen Gross <jgross@suse.com>
To: Paul Durrant <Paul.Durrant@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"netdev@vger.kernel.orga" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: Re: [Xen-devel] [PATCH resend] xen-netback: switch to threaded irq for control ring
Date: Thu, 22 Sep 2016 12:16:59 +0200 [thread overview]
Message-ID: <2f3c7f1b-6a36-8aaa-e10a-41a1d2cf37d8@suse.com> (raw)
In-Reply-To: <37d32749052f4ff887c5637671085389@AMSPEX02CL03.citrite.net>
On 22/09/16 11:09, Paul Durrant wrote:
>> -----Original Message-----
>> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of
>> Juergen Gross
>> Sent: 22 September 2016 10:03
>> To: xen-devel@lists.xenproject.org; netdev@vger.kernel.orga; linux-
>> kernel@vger.kernel.org
>> Cc: Juergen Gross <jgross@suse.com>; Wei Liu <wei.liu2@citrix.com>
>> Subject: [Xen-devel] [PATCH resend] xen-netback: switch to threaded irq for
>> control ring
>>
>> Instead of open coding it use the threaded irq mechanism in xen-netback.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>
> How have you tested this change?
Only compile-tested and loaded the module. As this feature isn't being
used in linux netfront AFAIK it is not easily testable. OTOH the code
modification is rather limited and I've used the threaded irq in the
Xen scsiback driver myself, so I'm rather confident it will work.
Juergen
next parent reply other threads:[~2016-09-22 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1474534964-15621-1-git-send-email-jgross@suse.com>
[not found] ` <37d32749052f4ff887c5637671085389@AMSPEX02CL03.citrite.net>
2016-09-22 10:16 ` Juergen Gross [this message]
2016-09-22 10:31 ` [Xen-devel] [PATCH resend] xen-netback: switch to threaded irq for control ring Paul Durrant
2016-09-22 10:39 ` Juergen Gross
2016-09-22 10:41 ` Paul Durrant
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=2f3c7f1b-6a36-8aaa-e10a-41a1d2cf37d8@suse.com \
--to=jgross@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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