All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Simon Martin <furryfuttock@gmail.com>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: Problems accessing passthrough PCI device
Date: Fri, 21 Nov 2014 12:26:03 -0500	[thread overview]
Message-ID: <20141121172602.GE8314@laptop.dumpdata.com> (raw)
In-Reply-To: <11981298.20141121135332@gmail.com>

On Fri, Nov 21, 2014 at 01:53:32PM -0300, Simon Martin wrote:
> Hello Konrad and Jan,
> 
> 
> > There was a bug in Xen pcibackend that I thought I upstreamed which could
> > be releated. It was not restoring the right registers to the PCI-device.
> 
> > They are attached.
> 
> Thanks for the patches, however I have been finding some very
> interesting things.
> 
> I decided to keep Xen out of the equation and booted into plain
> vanilla Linux. I then ran the FLR and got the same problem in the PCI
> configuration, all BARs were set to 0 and all reads to the PCI memory
> returned ff. I then manually wrote the correct values into the
> PCI BAR registers, and hey presto, reads to the PCI memory started
> working again!
> 
> Looks like my workaround for moment will be to store the PCI
> configuration registers before and resetting them after. Not cool, but
> something really strange is going on...

Right. Which is what the pciback does now (minus the bugs that the
two patches fix).

Look for pci_restore_config and pci_save_config
> 
> Thanks for your help.
> 
> Regards.
> 
> 
> -- 
> Best regards,
>  Simon                            mailto:furryfuttock@gmail.com
> 

  reply	other threads:[~2014-11-21 17:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 13:29 Problems accessing passthrough PCI device Simon Martin
2014-11-13 14:08 ` Jan Beulich
2014-11-13 15:07   ` Simon Martin
2014-11-13 15:52     ` Jan Beulich
2014-11-13 17:49       ` Simon Martin
2014-11-13 19:03         ` Konrad Rzeszutek Wilk
2014-11-13 19:21           ` Simon Martin
2014-11-13 19:29             ` Konrad Rzeszutek Wilk
2014-11-18 16:25               ` Simon Martin
2014-11-14  8:27         ` Jan Beulich
2014-11-18 16:24           ` Simon Martin
2014-11-18 16:49             ` Jan Beulich
2014-11-19 15:12               ` Simon Martin
2014-11-19 20:53                 ` Konrad Rzeszutek Wilk
2014-11-21 16:53                   ` Simon Martin
2014-11-21 17:26                     ` Konrad Rzeszutek Wilk [this message]
2014-11-20  8:51                 ` 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=20141121172602.GE8314@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=furryfuttock@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.