public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, Carsten Otte <cotte@de.ibm.com>,
	kvm-ia64-devel@lists.sourceforge.net,
	Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH 1/2] kvm-s390: provide get/set_mp_state stubs to fix	compile error
Date: Wed, 16 Apr 2008 14:44:21 -0300	[thread overview]
Message-ID: <20080416174421.GA14760@dmt> (raw)
In-Reply-To: <200804161121.05649.hollisb@us.ibm.com>

On Wed, Apr 16, 2008 at 11:21:05AM -0500, Hollis Blanchard wrote:
> By the way Marcelo, it would be polite to provide these stubs yourself to 
> avoid breaking the build on other architectures.

Indeed, should have been more careful.

> It looks like IA64 is still broken because of this.

Now I'm not sure if IA64 supports migration. Should it return -EINVAL or
the ia64 mpstate ?


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

  reply	other threads:[~2008-04-16 17:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1208354539.6122.6.camel@cotte.boeblingen.de.ibm.com>
2008-04-16 14:06 ` [PATCH 1/2] kvm-s390: provide get/set_mp_state stubs to fix compile error Carsten Otte
2008-04-16 16:21   ` Hollis Blanchard
2008-04-16 17:44     ` Marcelo Tosatti [this message]
2008-04-17  8:18       ` Avi Kivity
2008-04-16 14:06 ` [PATCH 2/2] virtio-s390: Change virtio interrupt definitions to follow architecture Carsten Otte
2008-04-17  8:44   ` Avi Kivity
2008-04-17  9:14     ` Christian Borntraeger
2008-04-17  9:27       ` 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=20080416174421.GA14760@dmt \
    --to=mtosatti@redhat.com \
    --cc=avi@qumranet.com \
    --cc=cotte@de.ibm.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=kvm-ia64-devel@lists.sourceforge.net \
    /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