xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: James Song <JSong@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: issue with c/s 21046 (was Re: [Patch] adjust the cpu-affinity to more than 64 cpus)
Date: Fri, 19 Mar 2010 11:10:21 +0000	[thread overview]
Message-ID: <4BA369AD0200007800035DF7@vpn.id2.novell.com> (raw)
In-Reply-To: 

That's in the qemu tree, so it has nothing to do with c/s 21046. Jan

>>> James Song 19.03.10 11:47 >>>
sorry, I forgot to post the error message, belowing is the error message:
helper2.c: In function a?cpu_x86_inita?:
helper2.c:142: error: a?shared_iopage_ta? has no member named a?vcpu_iodataa?
helper2.c: In function a?sp_infoa?:
helper2.c:219: error: a?shared_iopage_ta? has no member named a?vcpu_iodataa?
helper2.c:224: warning: format a?%lxa? expects type a?long unsigned inta?, but argument 6 has type a?uint32_ta?
helper2.c:224: warning: format a?%lxa? expects type a?long unsigned inta?, but argument 7 has type a?uint32_ta?
helper2.c:226: error: a?ioreq_ta? has no member named a?io_counta?
helper2.c: In function a?__cpu_get_ioreqa?:
helper2.c:235: error: a?shared_iopage_ta? has no member named a?vcpu_iodataa?
helper2.c:242: warning: format a?%lxa? expects type a?long unsigned inta?, but argument 7 has type a?uint32_ta?
helper2.c:242: warning: format a?%lxa? expects type a?long unsigned inta?, but argument 8 has type a?uint32_ta?
helper2.c: In function a?cpu_handle_ioreqa?:
helper2.c:517: warning: format a?%lxa? expects type a?long unsigned inta?, but argument 7 has type a?uint32_ta?
helper2.c:517: warning: format a?%lxa? expects type a?long unsigned inta?, but argument 8 has type a?uint32_ta

>>> Jan Beulich 2010-3-19 17:39 >>>
>>> "James Song" <jsong@novell.com> 19.03.10 10:09 >>>
>B.T.W, there are something wrong when compile c/s 21046! 

Mind stating what it is that is wrong with this?

Jan

  parent reply	other threads:[~2010-03-19 11:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17  8:56 [Patch] adjust the cpu-affinity to more than 64 cpus James (song wei)
2010-03-17  9:25 ` Jan Beulich
2010-03-18  2:26   ` James (song wei)
2010-03-18  3:41     ` James (song wei)
2010-03-19  3:14       ` Masaki Kanno
2010-03-19  9:09         ` James Song
2010-03-19  9:39           ` issue with c/s 21046 (was Re: [Patch] adjust the cpu-affinity to more than 64 cpus) Jan Beulich
2010-03-19 10:28           ` [Patch] adjust the cpu-affinity to more than64 cpus Masaki Kanno
2010-03-19 10:47           ` issue with c/s 21046 (was Re: [Patch] adjust the cpu-affinity to more than 64 cpus) James Song
2010-03-19 11:10           ` Jan Beulich [this message]
2010-03-30 18:23           ` [Patch] adjust the cpu-affinity to more than 64 cpus Liu, Jinsong
2010-03-31  2:12             ` James Song
2010-03-31  6:29             ` Masaki Kanno
2010-03-31  8:26               ` Liu, Jinsong

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=4BA369AD0200007800035DF7@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=JSong@novell.com \
    --cc=xen-devel@lists.xensource.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 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).