xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH v4 RFC 6/6] x86/MSI: properly track guest masking requests
Date: Wed, 24 Jun 2015 18:24:45 +0100	[thread overview]
Message-ID: <558AE7DD.6090908@citrix.com> (raw)
In-Reply-To: <55883D290200007800087A67@mail.emea.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1879 bytes --]

On 22/06/15 15:51, Jan Beulich wrote:
> ... by monitoring writes to the mask register.
>
> This allows reverting the main effect of the XSA-129 patches in qemu.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/arch/x86/msi.c
> +++ b/xen/arch/x86/msi.c
> @@ -1308,6 +1308,39 @@ printk("%04x:%02x:%02x.%u: MSI-X %03x:%u
>          return 1;
>      }
>  
> +    entry = find_msi_entry(pdev, -1, PCI_CAP_ID_MSI);
> +    if ( entry && entry->msi_attrib.maskbit )
> +    {
> +        uint16_t cntl;
> +        uint32_t unused;
> +
> +        pos = entry->msi_attrib.pos;
> +        if ( reg < pos || reg >= entry->msi.mpos + 8 )
> +            return 0;
> +printk("%04x:%02x:%02x.%u: MSI %03x:%u->%04x\n", seg, bus, slot, func, reg, size, *data);//temp
> +
> +        if ( reg == msi_control_reg(pos) )
> +            return size == 2 ? 1 : -EACCES;
> +        if ( reg < entry->msi.mpos || reg >= entry->msi.mpos + 4 || size != 4 )
> +            return -EACCES;

Can we avoid using EACCES to avoid confusing it with a mismatched tools
version?

~Andrew

> +
> +        cntl = pci_conf_read16(seg, bus, slot, func, msi_control_reg(pos));
> +        unused = ~(uint32_t)0 >> (32 - multi_msi_capable(cntl));
> +        for ( pos = 0; pos < entry->msi.nvec; ++pos, ++entry )
> +        {
> +            entry->msi_attrib.guest_masked =
> +                *data >> entry->msi_attrib.entry_nr;
> +            if ( entry->msi_attrib.host_masked )
> +                *data |= 1 << pos;
> +            unused &= ~(1 << pos);
> +        }
> +printk("%04x:%02x:%02x.%u: MSI -> %08x (%08x)\n", seg, bus, slot, func, *data, unused);//temp
> +
> +        *data |= unused;
> +
> +        return 1;
> +    }
> +
>      return 0;
>  }
>  
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


[-- Attachment #1.2: Type: text/html, Size: 2731 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-06-24 17:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 14:38 [PATCH v4 RFC 0/6] x86/MSI: XSA-120, 126, 128-131 follow-up Jan Beulich
2015-06-22 14:46 ` [PATCH v4 RFC 1/6] x86/PCI: add config space write abstract intercept logic Jan Beulich
2015-06-22 19:31   ` Konrad Rzeszutek Wilk
2015-06-23  7:21     ` Jan Beulich
2015-06-23 11:06       ` Konrad Rzeszutek Wilk
2015-06-23 12:55         ` Jan Beulich
2015-06-24 17:09   ` Andrew Cooper
2015-06-22 14:47 ` [PATCH v4 RFC 2/6] x86/MSI-X: track host and guest mask‑all requests separately Jan Beulich
2015-06-24 17:15   ` Andrew Cooper
2015-06-25  8:01     ` Jan Beulich
2015-06-25 14:25       ` Andrew Cooper
2015-06-22 14:49 ` [PATCH v4 3/6] x86/MSI-X: be more careful during teardown Jan Beulich
2015-06-22 14:50 ` [PATCH v4 4/6] x86/MSI-X: access MSI-X table only after having enabled MSI-X Jan Beulich
2015-06-22 14:51 ` [PATCH v4 RFC 5/6] x86/MSI-X: reduce fiddling with control register during restore Jan Beulich
2015-06-22 14:51 ` [PATCH v4 RFC 6/6] x86/MSI: properly track guest masking requests Jan Beulich
2015-06-24 17:24   ` Andrew Cooper [this message]
2015-06-25  8:04     ` Jan Beulich
2015-06-25 14:26       ` Andrew Cooper
2015-06-25 14:49         ` Jan Beulich
2015-07-13 11:42 ` [PATCH v4 RFC 0/6] x86/MSI: XSA-120, 126, 128-131 follow-up Jan Beulich

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=558AE7DD.6090908@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --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;
as well as URLs for NNTP newsgroup(s).