From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: andrew.cooper3@citrix.com, xen-devel@lists.xen.org, keir@xen.org,
linux@eikelenboom.it
Subject: Re: [PATCH V2] x86/AMD-Vi: Add additional check for invalid special->handle
Date: Wed, 11 Sep 2013 17:31:18 -0500 [thread overview]
Message-ID: <5230EF36.6030103@amd.com> (raw)
In-Reply-To: <52284B8502000078000F0A75@nat28.tlf.novell.com>
On 9/5/2013 2:14 AM, Jan Beulich wrote:
>>>> On 05.09.13 at 00:48, Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> wrote:
>> On 9/4/2013 4:57 AM, Jan Beulich wrote:
>>> It would, btw, be possible to get along with a single command line
>>> option, just having two alternating forms:
>>>
>>> ivrs_ioapic[id]=<sbdf>
>>> ivrs_ioapic[<sbdf>]=<id>
>> After looking through the examples above, I still think we only need the
>> "ivrs_ioapic[<sbdf>]=<id>" version.
> Perhaps, but then could you talk to your Linux side colleagues to
> find out why they picked (only) the other alternative? I'd really
> like to keep such workarounds largely in sync (a superset is fine,
> but a subset, not to speak of a disjoint set, are not) with Linux...
>
> Jan
At this point, I think it's mainly syntax. Since the implementation is
different. If you want to keep the syntax the same (i.e.
ivrs_ioapic[id]=<sdbf>), we can do that. I don't think Linux tries to
interpret as "pin id" or "pin sdbf". All it does is just ties both
values together.
Suravee
next prev parent reply other threads:[~2013-09-11 22:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 17:34 [PATCH V2] x86/AMD-Vi: Add additional check for invalid special->handle suravee.suthikulpanit
2013-08-29 7:17 ` Jan Beulich
2013-08-29 20:26 ` Suravee Suthikulpanit
2013-08-30 8:06 ` Jan Beulich
2013-08-30 20:35 ` Suravee Suthikulpanit
2013-09-04 9:57 ` Jan Beulich
2013-09-04 22:48 ` Suravee Suthikulpanit
2013-09-05 7:14 ` Jan Beulich
2013-09-11 22:31 ` Suravee Suthikulpanit [this message]
2013-09-12 7:11 ` Jan Beulich
2013-09-12 8:50 ` Jan Beulich
2013-09-12 18:02 ` Suravee Suthikulpanit
2013-09-12 18:03 ` Suravee Suthikulpanit
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=5230EF36.6030103@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).