Date: Thu, 19 Mar 2020 14:57:57 +1100 From: Jason Tubnor <jason@tubnor.net> To: Wanpeng Qian <wanpengqian@gmail.com> Cc: John-Mark Gurney <jmg@funkthat.com>, FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: bhyve: passthrough SMART info from host nvme controller Message-ID: <CACLnyC%2BUn0v5TQ=sLQ0e7gEFXPPU=VHbcmtyukX-Wy3=p0zkwQ@mail.gmail.com> In-Reply-To: <CANBJ%2BxTVV3gOv7%2B8Qq9Aq1PaHEo=W%2BNMuqMwZCD7uvU80NFLmA@mail.gmail.com> References: <CANBJ%2BxRdvTUHV0PQeBK2y2bCWDi5idqrD-AsHCT02fWkBLzeQQ@mail.gmail.com> <20200318175901.GI4213@funkthat.com> <CANBJ%2BxTVV3gOv7%2B8Qq9Aq1PaHEo=W%2BNMuqMwZCD7uvU80NFLmA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Thu, 19 Mar 2020 at 14:09, Wanpeng Qian <wanpengqian@gmail.com> wrote: > > Can't you do what something like pci_passthru.c does in passthru_init, > > and open /dev/nvme0 in pci_nvme_init? > > Yes, you are correct. but that will make /dev/nvme0 keep open all the time. > I just thinking when guest fire a logpage command, open the /dev/nvme0 > and get the SMART info. then close /dev/nvme0. So are you implying that it is safe for a guest to send such a call at anytime? For those that use bhyve for isolation, this sort of facility would be problematic not to mention insecure.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACLnyC%2BUn0v5TQ=sLQ0e7gEFXPPU=VHbcmtyukX-Wy3=p0zkwQ>