All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com, mtosatti@redhat.com
Subject: Re: [RFC PATCH] KVM: optimize apic interrupt delivery
Date: Mon, 10 Sep 2012 20:05:22 +0300	[thread overview]
Message-ID: <20120910170522.GC25827@redhat.com> (raw)
In-Reply-To: <20120910161754.GB25827@redhat.com>

On Mon, Sep 10, 2012 at 07:17:54PM +0300, Gleb Natapov wrote:
> > > +	return 0;
> > > +}
> > > +
> > > +static inline int kvm_apic_set_id(struct kvm_lapic *apic, u8 id)
> > > +{
> > > +	apic_set_reg(apic, APIC_ID, id << 24);
> > > +	return recalculate_apic_map(apic->vcpu->kvm);
> > > +}
> > > +
> > > +static inline int kvm_apic_set_ldr(struct kvm_lapic *apic, u32 id)
> > > +{
> > > +	apic_set_reg(apic, APIC_LDR, id);
> > > +	return recalculate_apic_map(apic->vcpu->kvm);
> > > +}
> > > +
> > 
> > return value of these functions seems never checked.
> > 
> Yes, the problem is that we can do nothing about the failure if failure
> happens during guest write.
> 
Actually I have an idea how to handle the error. Never return one. If
map cannot be allocated go slow path always. phys_map should be checked
for NULL during delivery in this case obviously.

--
			Gleb.

  reply	other threads:[~2012-09-10 17:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 13:09 [RFC PATCH] KVM: optimize apic interrupt delivery Gleb Natapov
2012-09-10 14:44 ` Michael S. Tsirkin
2012-09-10 16:17   ` Gleb Natapov
2012-09-10 17:05     ` Gleb Natapov [this message]
2012-09-11  9:29       ` Avi Kivity
2012-09-11  9:35         ` Gleb Natapov
2012-09-11  9:41           ` Avi Kivity
2012-09-11  9:45             ` Gleb Natapov
2012-09-11  9:57               ` Gleb Natapov
2012-09-11 12:05                 ` Avi Kivity
2012-09-11 12:12                   ` Gleb Natapov
2012-09-11 12:04               ` Avi Kivity
2012-09-11 12:09                 ` Gleb Natapov
2012-09-11 11:20     ` Gleb Natapov
2012-09-11 11:49       ` Gleb Natapov
2012-09-10 15:09 ` Avi Kivity
2012-09-10 15:35   ` Gleb Natapov

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=20120910170522.GC25827@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.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.