xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Weidong Han <weidong.han@intel.com>
To: "Nadolski, Ed" <Ed.Nadolski@lsi.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Kay, Allen M" <allen.m.kay@intel.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] VT-d: should not disable VT-d when find unknown DMAR structure type
Date: Fri, 26 Mar 2010 10:16:48 +0800	[thread overview]
Message-ID: <4BAC1910.7000304@intel.com> (raw)
In-Reply-To: <8115AF16522A3D4383C1FF753036713F9B3AB29B@cosmail01.lsi.com>

Nadolski, Ed wrote:
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
>> bounces@lists.xensource.com] On Behalf Of Han, Weidong
>> Sent: Thursday, March 25, 2010 3:41 AM
>> To: xen-devel@lists.xensource.com
>> Cc: Kay, Allen M; Keir Fraser
>> Subject: [Xen-devel] [PATCH] VT-d: should not disable VT-d when find
>> unknown DMAR structure type
>>
>> Now 4 DMAR structure types are supported (type value 0 ~ 3). Type
>> values > 3 are reserved for future use. Current implementation disables
>> VT-d when find unknown DMAR structure type, this may lead to VT-d
>> disabling on future platforms before supporting new types on Xen. For
>> forward compatibility, just skip unknown structures by skipping the
>> appropriate number of bytes indicated by the Length field, and then VT-
>> d still can be used.
>>
>> Signed-off-by: Weidong Han <weidong.han@intel.com>
>>
>> diff -r 298794763a75 xen/drivers/passthrough/vtd/dmar.c
>> --- a/xen/drivers/passthrough/vtd/dmar.c	Fri Mar 26 02:04:06 2010
>> +0800
>> +++ b/xen/drivers/passthrough/vtd/dmar.c	Fri Mar 26 02:08:45 2010
>> +0800
>> @@ -730,7 +730,6 @@ static int __init acpi_parse_dmar(struct
>>              dprintk(XENLOG_WARNING VTDPREFIX,
>>                      "Unknown DMAR structure type %x\n",
>>                      entry_header->type);
>> -            ret = -EINVAL;
>>              break;
>>          }
>>          if ( ret )
>>     
>
> Just a suggestion: Since this completely changes the meaning of the dprintk message, the message should state that the unknown DMAR is being ignored. Otherwise an end user might think that it means some kind of serious problem.
>
> Ed
>   
Good suggestion. Changed the warning message as below.

Signed-off-by: Weidong Han <weidong.han@intel.com>

diff -r 18f4db5f72d7 xen/drivers/passthrough/vtd/dmar.c
--- a/xen/drivers/passthrough/vtd/dmar.c    Thu Mar 25 10:01:05 2010 +0000
+++ b/xen/drivers/passthrough/vtd/dmar.c    Fri Mar 26 10:12:32 2010 +0800
@@ -711,7 +711,7 @@ static int __init acpi_parse_dmar(struct
             break;
         default:
             dprintk(XENLOG_WARNING VTDPREFIX,
-                    "Unknown DMAR structure type %x\n",
+                    "Ignore unknown DMAR structure type (0x%x)\n",
                     entry_header->type);
             break;
         }

      reply	other threads:[~2010-03-26  2:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  9:40 [PATCH] VT-d: should not disable VT-d when find unknown DMAR structure type Han, Weidong
2010-03-25 14:35 ` Nadolski, Ed
2010-03-26  2:16   ` Weidong Han [this message]

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=4BAC1910.7000304@intel.com \
    --to=weidong.han@intel.com \
    --cc=Ed.Nadolski@lsi.com \
    --cc=allen.m.kay@intel.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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).