xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Huang2, Wei" <Wei.Huang2@amd.com>,
	Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.0 is broken on 32bit
Date: Thu, 8 Jul 2010 08:02:14 +0100	[thread overview]
Message-ID: <C85B3686.19B10%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <EE335F95F28A664DB4A21289D2AA053B436943DF@SAUSEXMBP01.amd.com>

On 08/07/2010 00:04, "Huang2, Wei" <Wei.Huang2@amd.com> wrote:

> The changset 21229 breaks Xen 4.0.1 tree on 32bit environment. Starting a
> guest VM will throw out an error as ³Error: (38, ŒFunction not implemented¹)².
> Apparently, the hypercall to mem_sharing_op is missing for 32bit environment
> due to 21229.  The following small patch can fix this issue.

This will be the unconditional xc.dom_set_memshr() call in xend's image.py.
Should be wrapped in try-except.

 -- Keir

> Thanks,
> -Wei
>  
>  
>  
> diff -r afe5a6a8b8df xen/arch/x86/domctl.c
> --- a/xen/arch/x86/domctl.c     Fri Jul 02 22:04:32 2010 +0100
> +++ b/xen/arch/x86/domctl.c     Wed Jul 07 11:51:26 2010 -0500
> @@ -1449,6 +1449,11 @@
>          } 
>      }
>      break;
> +#else
> +    case XEN_DOMCTL_mem_event_op:
> +    case XEN_DOMCTL_mem_sharing_op:
> +        ret = 0;
> +        break;
>  #endif /* __x86_64__ */
>  
>      default:
> 

  reply	other threads:[~2010-07-08  7:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 23:04 Xen 4.0 is broken on 32bit Huang2, Wei
2010-07-08  7:02 ` Keir Fraser [this message]
2010-07-08  9:05 ` Keir Fraser

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=C85B3686.19B10%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=Wei.Huang2@amd.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).