All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Ruh <jan.ruh@tttech.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: AW: Kernel requires x86-64 CPU, after modifying arch_shared_info struct
Date: Tue, 30 Jun 2020 07:30:14 +0000	[thread overview]
Message-ID: <f28eeb9141a74dde97b9fb84080a99a2@tttech.com> (raw)
In-Reply-To: <20200629101728.GH735@Air-de-Roger>

Hi Roger,

thanks for your time, your remark that you cannot see how it has to do with the shared_info got me to step-by-step revert all changes I have done. Turns out a few weeks ago when implementing a sysctl I must have accidentally deleted the architecture specific syctl in the default case of the common sysctl. This leads to Xen quietly defaulting to a x86_32 CPU.

Jan.
CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail@tttech.com immediately.


      reply	other threads:[~2020-06-30  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29  7:43 Kernel requires x86-64 CPU, after modifying arch_shared_info struct Jan Ruh
2020-06-29  9:18 ` Roger Pau Monné
2020-06-29  9:56   ` AW: " Jan Ruh
2020-06-29 10:17     ` Roger Pau Monné
2020-06-30  7:30       ` Jan Ruh [this message]

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=f28eeb9141a74dde97b9fb84080a99a2@tttech.com \
    --to=jan.ruh@tttech.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.