public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Hollis Blanchard
	<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
	"Zhang,
	Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH]3/5 Using kvm_arch prefix to define	functions, and replace
Date: Mon, 12 Nov 2007 11:50:54 +0200	[thread overview]
Message-ID: <473821FE.3060608@qumranet.com> (raw)
In-Reply-To: <473819EF.2090301-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>

Carsten Otte wrote:
> Avi Kivity wrote:
>   
>> For the present discussion, I agree, but in general we should be 
>> prepared to accept some no-op callouts.
>>     
>
> Oh sure, I don't mind those. We'll have plenty of them, where other 
> architectures will need to take action and s390 won't. It's just that 
> in the current location, the common code would do
>
> common_func() {
> 	loop {
> 		arch_callback();
> 	}
> }
> And I suggested to make the whole thing a callback.
>   

Ah, agreed.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-11-12  9:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08  7:21 [PATCH]3/5 Using kvm_arch prefix to define functions, and replace Zhang, Xiantao
     [not found] ` <42DFA526FC41B1429CE7279EF83C6BDC905005-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-08 13:49   ` Carsten Otte
     [not found]     ` <473313D8.4010604-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-11-08 15:05       ` [PATCH]3/5 Using kvm_arch prefix to definefunctions, " Zhang, Xiantao
     [not found]         ` <42DFA526FC41B1429CE7279EF83C6BDC94EE5E-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-11 10:48           ` Avi Kivity
2007-11-08 20:18       ` [PATCH]3/5 Using kvm_arch prefix to define functions, " Hollis Blanchard
2007-11-09  9:01         ` Carsten Otte
     [not found]           ` <473421E7.2070205-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-11-11 10:49             ` Avi Kivity
     [not found]               ` <4736DE50.5010200-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-12  9:16                 ` Carsten Otte
     [not found]                   ` <473819EF.2090301-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-11-12  9:50                     ` Avi Kivity [this message]
2007-11-08 20:57   ` Hollis Blanchard
2007-11-09  7:25     ` [PATCH]3/5 Using kvm_arch prefix to define functions, andreplace Zhang, Xiantao

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=473821FE.3060608@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
    --cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox