xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Grodzovsky <andrey2805@gmail.com>
To: xen-devel@lists.xen.org
Cc: "Jürgen Walter • Quattru" <jw@quattru.com>
Subject: Re: Issues with PCI-Passtrough (VT-d) in HVM with Xen 4.6
Date: Wed, 15 Jun 2016 06:45:22 -0400	[thread overview]
Message-ID: <CAJphD_o27ySbiwkmdbYsW-HkkEct0nwEKEfa-xTs79dbVmPn9A@mail.gmail.com> (raw)


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

In reply to -
http://lists.xen.org/archives/html/xen-devel/2016-06/msg00622.html

HI, I am working with Jurgen on the issue, as per Jan's request I tried to
write explicitly only latency timer to be written -
bool force_write = false;
if ((dev_data->permissive || xen_pcibk_permissive) &&
              offset == PCI_CACHE_LINE_SIZE && size == 4)
             force_write = true;
...

if ((force_write || !handled) && !err) {...}

But then it exposed another issue, the command register field seems not to
be restored also
because I think the bits which are to be restored are not
in PCI_COMMAND_GUEST mask.

The only hack which always works for me is force write even if the
confpsace fields filter doens't allow it -

+       int remainder = size;
+
        if (unlikely(verbose_request))
                printk(KERN_DEBUG
                       DRV_NAME ": %s: write request %d bytes at 0x%x =
%x\n",
@@ -252,10 +254,11 @@ int xen_pcibk_config_write(struct pci_dev *dev, int
offset, int size, u32 value)
                         * special helpers to work correctly.
                         */
                        handled = 1;
+                       remainder -= field->size
                }
        }

-       if (!handled && !err) {
+       if ((remainder || !handled) && !err) {


Thanks.

Andrey Grodzovsky.

[-- Attachment #1.2: Type: text/html, Size: 2029 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:[~2016-06-15 10:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 10:45 Andrey Grodzovsky [this message]
2016-06-15 13:14 ` Issues with PCI-Passtrough (VT-d) in HVM with Xen 4.6 Jan Beulich
2016-06-18  3:24   ` Andrey Grodzovsky
2016-06-20  6:57     ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2016-06-02 19:59 Sylwester Sosnowski
2016-06-02 20:06 ` Konrad Rzeszutek Wilk
2016-06-02 20:11   ` Sylwester Sosnowski
2016-06-03  7:24 ` Sylwester Sosnowski
2016-06-03 11:52 ` Jan Beulich
2016-06-03 12:02   ` Jürgen Walter
2016-06-03 13:26     ` Jan Beulich
2016-06-03 14:20       ` Jan Beulich
2016-06-04 14:36         ` Jürgen Walter
2016-06-06  7:59           ` Jan Beulich
2016-06-04 15:15       ` Jürgen Walter
2016-06-06  8:41         ` Jan Beulich
2016-06-06  9:09           ` Jürgen Walter
2016-06-06  9:43             ` Jan Beulich
2016-06-06 14:01           ` Boris Ostrovsky
2016-06-06 14:21             ` Jan Beulich
2016-06-06 14:45               ` Boris Ostrovsky
2016-06-02 19:49 Sylwester Sosnowski

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=CAJphD_o27ySbiwkmdbYsW-HkkEct0nwEKEfa-xTs79dbVmPn9A@mail.gmail.com \
    --to=andrey2805@gmail.com \
    --cc=jw@quattru.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).