qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] Move some declarations around in the QEMU CharDriver code
Date: Mon, 27 Oct 2008 15:46:51 -0500	[thread overview]
Message-ID: <490628BB.70406@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580810240712g73a2d6a5ue8959ce94f76a270@mail.gmail.com>

Blue Swirl wrote:
> On 10/23/08, Anthony Liguori <aliguori@us.ibm.com> wrote:
>   
>> The goal of this series is to move the CharDriverState code out of vl.c and
>>  into its own file, qemu-char.c.  This patch moves around some declarations so
>>  the next patch can be pure code motion.
>>     
>
> Good idea. Do you plan to do this for other things, for example network code?
>   

Yes, I have patches in queue to move out the networking code, the timer 
code, and the main loop.  I have two goals here.  A lot of the vl.c code 
is target independent so I'd like to move a lot of that code to be 
compiled once for all targets.  I also want to be able to reuse the main 
loop in things like qemu-nbd so that it can be fully asychronous without 
needing to rewrite all of that code.

I'll go ahead and commit the CharDriverState movement and post the next 
movement patch in a couple days.

>   
>>  -static inline int send_all(int fd, const uint8_t *buf, int len1)
>>  +inline int send_all(int fd, const uint8_t *buf, int len1)
>>     
>
> The 'inline' looks a bit odd without 'static'.
>   

Yeah, I'll fix that.  Didn't notice that for whatever reason.

Regards,

Anthony Liguori

      parent reply	other threads:[~2008-10-27 20:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 19:39 [Qemu-devel] [PATCH 1/2] Move some declarations around in the QEMU CharDriver code Anthony Liguori
2008-10-23 19:39 ` [Qemu-devel] [PATCH 2/2] Move CharDriverState code out of vl.c Anthony Liguori
2008-10-24 14:12 ` [Qemu-devel] [PATCH 1/2] Move some declarations around in the QEMU CharDriver code Blue Swirl
2008-10-24 14:18   ` Gerd Hoffmann
2008-10-27 20:48     ` Anthony Liguori
2008-10-27 20:46   ` 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=490628BB.70406@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).