From: Gerd Hoffmann <kraxel@redhat.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: wei.liu2@citrix.com, seabios@seabios.org,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
xen-devel <xen-devel@lists.xen.org>,
kevin@koconnor.net, Shannon Zhao <zhaoshenglong@huawei.com>,
keir@xen.org, evil.dani@gmail.com,
"Jinjian (Ken)" <jinjian@huawei.com>
Subject: Re: [SeaBIOS] Xen PV block device support in Seabios
Date: Wed, 16 Mar 2016 13:58:33 +0100 [thread overview]
Message-ID: <1458133113.30910.19.camel__11866.3950743668$1458133192$gmane$org@redhat.com> (raw)
In-Reply-To: <1458130952.30744.14.camel@hellion.org.uk>
Hi,
> > Ian, thanks for your reply! It looks like the problem is how and when to
> > clear PV resources in seabios before handing over to guest. But I wonder
> > why virtio works in seabios. Does seabios using virtio need to clear
> > things like vrings? Or seabios doesn't clear the things and guest just
> > covers the configuration with new values?
>
> I think virtio covered this use case from day 1 by having the reset,
That is correct. First thing the kernel driver does as part of the
initialization sequence is a reset, to put the device into a known
state, no matter where seabios left it off.
Oh, and of course seabios does the same. So even in case the virtio
device is in some weird state due to kernel crashing and rebooting
seabios will be able to boot from it without any problems.
cheers,
Gerd
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-16 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 3:33 Xen PV block device support in Seabios Shannon Zhao
2016-03-16 10:39 ` Wei Liu
2016-03-16 11:20 ` [SeaBIOS] " Ian Campbell
2016-03-16 12:13 ` Shannon Zhao
2016-03-16 12:22 ` Ian Campbell
[not found] ` <1458130952.30744.14.camel@hellion.org.uk>
2016-03-16 12:31 ` Shannon Zhao
2016-03-16 12:58 ` Gerd Hoffmann [this message]
2016-03-16 13:15 ` Konrad Rzeszutek Wilk
2016-03-16 13:33 ` Jan Beulich
2016-03-16 13:41 ` Ian Campbell
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='1458133113.30910.19.camel__11866.3950743668$1458133192$gmane$org@redhat.com' \
--to=kraxel@redhat.com \
--cc=evil.dani@gmail.com \
--cc=ijc@hellion.org.uk \
--cc=jinjian@huawei.com \
--cc=keir@xen.org \
--cc=kevin@koconnor.net \
--cc=peter.huangpeng@huawei.com \
--cc=seabios@seabios.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zhaoshenglong@huawei.com \
/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).