All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Zhang, Yang" <yang.zhang@intel.com>
Cc: "kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH] KVM: IA64: enable external interrupt in vmm
Date: Wed, 25 Mar 2009 13:54:03 +0200	[thread overview]
Message-ID: <49CA1B5B.6090107@redhat.com> (raw)
In-Reply-To: <10C63FAD690C13458F0B32BCED571F140E29AF98@pdsmsx502.ccr.corp.intel.com>

Zhang, Yang wrote:
> Avi Kivity wrote:
>   
>> I'm surprised it doesn't work this way already.  What happens now if
>> the guest disables interrupts and spins?
>>     
> when vmm disables interrupt, all the external interrupts are pending 
> until return back to the guest. and this will degrade the i/o performance.

Oh I misunderstood.  When the guest us running interrupts are enabled, 
this was true before.  The change enables interrupts in the monitor, so 
it improves responsiveness.

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


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH] KVM: IA64: enable external interrupt in vmm
Date: Wed, 25 Mar 2009 11:54:03 +0000	[thread overview]
Message-ID: <49CA1B5B.6090107@redhat.com> (raw)
In-Reply-To: <10C63FAD690C13458F0B32BCED571F140E29AF79@pdsmsx502.ccr.corp.intel.com>

Zhang, Yang wrote:
> Avi Kivity wrote:
>   
>> I'm surprised it doesn't work this way already.  What happens now if
>> the guest disables interrupts and spins?
>>     
> when vmm disables interrupt, all the external interrupts are pending 
> until return back to the guest. and this will degrade the i/o performance.

Oh I misunderstood.  When the guest us running interrupts are enabled, 
this was true before.  The change enables interrupts in the monitor, so 
it improves responsiveness.

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


  reply	other threads:[~2009-03-25 11:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 10:27 [PATCH] KVM: IA64: enable external interrupt in vmm Zhang, Yang
2009-03-25 10:27 ` Zhang, Yang
2009-03-25 10:35 ` Avi Kivity
2009-03-25 10:35   ` Avi Kivity
2009-03-25 11:45   ` Zhang, Yang
2009-03-25 11:45     ` Zhang, Yang
2009-03-25 11:54     ` Avi Kivity [this message]
2009-03-25 11:54       ` Avi Kivity
2009-03-25 11:57       ` Zhang, Yang
2009-03-25 11:57         ` Zhang, Yang
2009-03-26  8:58 ` Avi Kivity
2009-03-26  8:58   ` Avi Kivity

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=49CA1B5B.6090107@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm-ia64@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=xiantao.zhang@intel.com \
    --cc=yang.zhang@intel.com \
    /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.