xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] VT-d: make remap_entry_to_msi_msg() return consistent message
Date: Tue, 02 Oct 2012 18:00:55 +0100	[thread overview]
Message-ID: <CC90DC57.4DACF%keir@xen.org> (raw)
In-Reply-To: <506B1C6E020000780009F221@nat28.tlf.novell.com>

On 02/10/2012 15:55, "Jan Beulich" <JBeulich@suse.com> wrote:

> During debugging of another problem I found that in x2APIC mode, the
> destination field of the low address value wasn't passed back
> correctly. While this is benign in most cases (as the value isn't being
> used anywhere), it can be confusing (and misguiding) when printing the
> value read or when comparing it to the one previously passed into the
> inverse function.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Acked-by: Keir Fraser <keir@xen.org>

> --- a/xen/drivers/passthrough/vtd/intremap.c
> +++ b/xen/drivers/passthrough/vtd/intremap.c
> @@ -504,7 +504,11 @@ static int remap_entry_to_msi_msg(
>              MSI_ADDR_REDIRECTION_CPU:
>              MSI_ADDR_REDIRECTION_LOWPRI);
>      if ( x2apic_enabled )
> +    {
>          msg->dest32 = iremap_entry->lo.dst;
> +        msg->address_lo |=
> +            (iremap_entry->lo.dst & 0xff) << MSI_ADDR_DEST_ID_SHIFT;
> +    }
>      else
>          msg->address_lo |=
>              ((iremap_entry->lo.dst >> 8) & 0xff ) << MSI_ADDR_DEST_ID_SHIFT;
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2012-10-02 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 14:55 [PATCH] VT-d: make remap_entry_to_msi_msg() return consistent message Jan Beulich
2012-10-02 17:00 ` Keir Fraser [this message]
2012-10-03 12:58   ` Jan Beulich
2012-10-03 14:33     ` Keir Fraser

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=CC90DC57.4DACF%keir@xen.org \
    --to=keir@xen.org \
    --cc=JBeulich@suse.com \
    --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).