Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Jul 2016 16:38:45 -0700
From:      Peter Grehan <grehan@freebsd.org>
To:        Tycho Nightingale <tycho.nightingale@pluribusnetworks.com>, Andriy Gapon <avg@FreeBSD.org>
Cc:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@FreeBSD.org>
Subject:   Re: bhyve: disable msi and msix on virtio reset?
Message-ID:  <22aa6570-6a2e-e5d6-1882-86b9ffcb15e7@freebsd.org>
In-Reply-To: <7D5D0A30-1ABA-49F6-83CC-6F398FC25B05@pluribusnetworks.com>
References:  <011771a3-8424-7810-d9db-870ddcea2448@FreeBSD.org> <7D5D0A30-1ABA-49F6-83CC-6F398FC25B05@pluribusnetworks.com>

index | next in thread | previous in thread | raw e-mail

Hi Tycho,

> Yes, writing 0 to the status resister should reset the device
> including all PCIE state.  This implies that vi_reset_dev() needs to
> take the proper actions to bring the associated pci_devinst (which
> from the guest’s perspective isn’t a discrete element) back to it’s
> reset state too.

  I'm not sure if the reset also hits PCIe state, if you're counting 
config space as part of that (e.g. BAR contents). As an example, the 
FreeBSD guest virtio code doesn't do any config space saves/restores 
around a reset.

later,

Peter.


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22aa6570-6a2e-e5d6-1882-86b9ffcb15e7>