Date: Wed, 2 Sep 2015 12:51:51 -0700 From: Conrad Meyer <cem@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org, jimharris@freebsd.org Subject: Re: svn commit: r287403 - head/sys/dev/ioat Message-ID: <CAG6CVpXum1bZYuv4k8W8Vp6WLnaXMURYMX%2BSTRzyUkByVUr_Uw@mail.gmail.com> In-Reply-To: <CAG6CVpUwYkd6Dv=LMbVm7KE_QJtMMYwcoXsG3shFj56asUP-PQ@mail.gmail.com> References: <201509021648.t82Gm451015184@repo.freebsd.org> <3589074.YABE6tqvK0@ralph.baldwin.cx> <CAG6CVpUwYkd6Dv=LMbVm7KE_QJtMMYwcoXsG3shFj56asUP-PQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
https://reviews.freebsd.org/D3552 On Wed, Sep 2, 2015 at 12:15 PM, Conrad Meyer <cem@freebsd.org> wrote: > On Wed, Sep 2, 2015 at 10:26 AM, John Baldwin <jhb@freebsd.org> wrote: >> Alternatively you could use pci_restore_state() (before reset) and >> pci_save_state() (after reset) to restore standard PCI config registers >> (including MSI/MSI-X) after a reset. >> >> This might be more scalable if you want to ensure other PCI config >> registers (e.g. PCI-e capabilities) are restored after a reset. > > > Hi John, > > Do you mean pci_save_state() before reset and pci_restore_state() > afterwards? Seems reasonable to me. > > Thanks, > Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpXum1bZYuv4k8W8Vp6WLnaXMURYMX%2BSTRzyUkByVUr_Uw>