From: Anthony Liguori <aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: virtio module backport
Date: Thu, 03 Jan 2008 09:16:06 -0600 [thread overview]
Message-ID: <477CFC36.7070002@us.ibm.com> (raw)
In-Reply-To: <477CCCE2.5090307-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Hi,
>>
>> I've posted a repo that contains my initial attempt at backporting
>> the virtio modules. I've tested against a 2.6.22, 2.6.20, and 2.6.18
>> kernel (although I haven't tried the block device against 2.6.18).
>> It requires Rusty's patch queue plus the three patches I just sent to
>> virtualization@l-f.
>>
>> The makefile supports a 'make sync LINUX=/path/to/linux' just like
>> the kvm-userspace/kernel directory does.
>>
>> This is still rough as I haven't went through and made sure all of
>> the #if's are right.
>>
>> http://hg.codemonkey.ws/virtio-ext-modules
>>
>>
>
> I think that 'typedef _Bool bool' is better than unsigned int, as it
> forces conversions to 0/1.
>
> Modern Linux uses _Bool as well.
>
Fair enough. I've updated.
Regards,
Anthony Liguori
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-01-03 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 21:04 virtio module backport Anthony Liguori
[not found] ` <477BFC6E.2040508-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-02 21:21 ` Anthony Liguori
2008-01-03 11:54 ` Avi Kivity
[not found] ` <477CCCE2.5090307-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-03 15:16 ` Anthony Liguori [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=477CFC36.7070002@us.ibm.com \
--to=aliguori-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.