From: Kevin O'Connor <kevin@koconnor.net>
To: Avi Kivity <avi@redhat.com>
Cc: Leendert van Doorn <leendert@paramecium.org>,
"'Shan, Haitao'" <haitao.shan@intel.com>,
"'Liu, Kechao'" <kechao.liu@intel.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH][v2] kvm-userspace: Load PCI option ROMs
Date: Sun, 4 Jan 2009 13:03:55 -0500 [thread overview]
Message-ID: <20090104180355.GA18629@morn.localdomain> (raw)
In-Reply-To: <4960F1D2.4080600@redhat.com>
On Sun, Jan 04, 2009 at 07:28:50PM +0200, Avi Kivity wrote:
> Leendert van Doorn wrote:
>> Avi wrote:
>>> This is worrying as it will cause us to diverge from upstream bochs bios.
>> Yep. I'll create a less invasive patch. I've been looking at SEABIOS which
>> seems a much better alternative but the GPLv3 license worries me, especially
>> when you have proprietary guests that calls back into it.
> Surely, the BIOS call interface is a GPL boundary, just like the Linux
> syscall interface. Kevin, is that not the case? If it is a GPL
> interface, can you add an explicit exception to make it clear?
I would not want the SeaBIOS license to extend to an emulator that
deploys SeaBIOS nor to any regular real-mode apps that call SeaBIOS
handlers. I'd be happy to make this explicit.
-Kevin
prev parent reply other threads:[~2009-01-04 18:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 3:51 [PATCH][v2] kvm-userspace: Load PCI option ROMs Liu, Kechao
2008-12-29 8:28 ` Avi Kivity
2008-12-29 9:36 ` Liu, Kechao
2008-12-29 9:49 ` Avi Kivity
2008-12-30 1:01 ` Shan, Haitao
2008-12-30 15:51 ` Avi Kivity
2008-12-31 2:06 ` Shan, Haitao
2008-12-31 9:28 ` Avi Kivity
2009-01-03 2:29 ` Shan, Haitao
2009-01-04 2:12 ` Shan, Haitao
2009-01-04 3:54 ` Leendert van Doorn
2009-01-04 4:58 ` Shan, Haitao
2009-01-04 10:26 ` Avi Kivity
2009-01-04 17:12 ` Leendert van Doorn
2009-01-04 17:28 ` Avi Kivity
2009-01-04 17:29 ` Avi Kivity
2009-01-04 17:54 ` Leendert van Doorn
2009-01-04 19:51 ` Avi Kivity
2009-01-04 18:03 ` Kevin O'Connor [this message]
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=20090104180355.GA18629@morn.localdomain \
--to=kevin@koconnor.net \
--cc=avi@redhat.com \
--cc=haitao.shan@intel.com \
--cc=kechao.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leendert@paramecium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox