From: Amit Shah <amit.shah@qumranet.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [kvm-devel] [PATCH 1/2] KVM userspace: Add PCI device passthrough support
Date: Thu, 8 Nov 2007 11:42:56 +0530 [thread overview]
Message-ID: <200711081142.56746.amit.shah@qumranet.com> (raw)
In-Reply-To: <1194465692.32757.2.camel@basalt>
On Thursday 08 November 2007 01:31:32 Hollis Blanchard wrote:
> I'm sorry these comments aren't substantive, but please watch your
> whitespace...
Hi Hollis,
Thanks for going through this. We know about these issues; the userspace is
kind of messy since it's collected from various sources and we are urging the
people who have done this to provide good patches.
These aren't ready yet for inclusion, we've sent them out to get comments on
the overall solution for PCI passthrough.
> On Wed, 2007-11-07 at 21:45 +0200, Amit Shah wrote:
> > diff --git a/qemu/Makefile b/qemu/Makefile
> > index 053c88c..3e599f3 100644
> > --- a/qemu/Makefile
> > +++ b/qemu/Makefile
> > @@ -37,7 +37,7 @@ qemu-img$(EXESUF): qemu-img.c cutils.c block.c
> > block-raw.c block-cow.c block-qco
> > dyngen$(EXESUF): dyngen.c
> > $(HOST_CC) $(CFLAGS) $(CPPFLAGS) $(BASE_CFLAGS) -o $@ $^
> >
> > -clean:
> > +clean:
> > # avoid old build problems by removing potentially incorrect old
> > files
> > rm -f config.mak config.h op-i386.h opc-i386.h gen-op-i386.h
> > op-arm.h opc-arm.h gen-op-arm.h
> > rm -f *.o *.a $(TOOLS) dyngen$(EXESUF) TAGS cscope.* *.pod *~
> > */*~
>
> Extra space.
>
> > @@ -88,8 +88,8 @@ endif
> > test speed test2: all
> > $(MAKE) -C tests $@
> >
> > -TAGS:
> > - etags *.[ch] tests/*.[ch]
> > +TAGS:
> > + etags *.[ch] tests/*.[ch] hw/passthrough/*.[ch]
> >
> > cscope:
> > rm -f ./cscope.*
>
> Another extra space.
>
> > diff --git a/qemu/exec.c b/qemu/exec.c
> > index 3e588d5..7a21ca5 100644
> > --- a/qemu/exec.c
> > +++ b/qemu/exec.c
> > @@ -2484,6 +2484,7 @@ int cpu_register_io_memory(int io_index,
> > if (io_mem_nb >= IO_MEM_NB_ENTRIES)
> > return -1;
> > io_index = io_mem_nb++;
> > + fprintf(stderr, "iomem index %d out of %d\n", io_index,
> > IO_MEM_NB_ENTRIES);
> > } else {
> > if (io_index >= IO_MEM_NB_ENTRIES)
> > return -1;
>
> Bad indentation.
>
> I didn't check the rest of your patches for this, so you should skim
> them...
prev parent reply other threads:[~2007-11-08 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cc1a3d4ee5e648e13b3c75fc62d9c6c00405c322.1194464687.git.amit.shah@qumranet.com>
2007-11-07 19:45 ` [Qemu-devel] [PATCH 1/2] KVM userspace: Add PCI device passthrough support Amit Shah
2007-11-08 6:28 ` [Qemu-devel] Re: [kvm-devel] " Avi Kivity
2007-11-08 9:19 ` [Qemu-devel] " Fabrice Bellard
2007-11-08 10:00 ` [kvm-devel] " Dor Laor
[not found] ` <95597be41c7ffbb889a0e53cb8294203ac6b5519.1194464687.git.amit.shah@qumranet.com>
2007-11-07 19:45 ` [Qemu-devel] [PATCH 2/2] KVM Userspace: IRQ injection into guest Amit Shah
2007-11-07 20:01 ` [Qemu-devel] Re: [kvm-devel] [PATCH 1/2] KVM userspace: Add PCI device passthrough support Hollis Blanchard
2007-11-08 6:12 ` Amit Shah [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=200711081142.56746.amit.shah@qumranet.com \
--to=amit.shah@qumranet.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).