All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raz <raziebe@gmail.com>
To: segher@kernel.crashing.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Looking for architecture papers
Date: Mon, 8 Oct 2018 19:44:12 +0300	[thread overview]
Message-ID: <CAPB=Z-qC+Xgwyb=WAD-r_TYWWRRrpLJT6jFzCfKLtkNVn_FDUg@mail.gmail.com> (raw)
In-Reply-To: <20181006122750.GF29268@gate.crashing.org>

Both systemsim and my powerpc server boots with MSR_HV=1, i.e, hypervisor state.
Is there away to fix that ? writing to the MSR cannot work according
the documentation ( and reality ).



On Sat, Oct 6, 2018 at 3:27 PM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> On Sat, Oct 06, 2018 at 12:19:45PM +0300, Raz wrote:
> > Hey
> > How does HVSC works ?
> > I looked in the code and LoPAR documentation. It looks like there is
> > vector called
> > system_call_pSeries ( at 0xc00 ) that is supposed to be called when we
> > invoke HVSC from kernel
> > mode.
> > Now, I wrote a NULL call HSVC and patched the exceptions-64s.S to
> > return RFID immediately.
> > This does not work.
> > Would you be so kind to explain how HVSC works ?
> > thank you
>
> If your kernel is not running in hypervisor mode, sc 1 does not call the
> kernel (but the hypervisor, instead).  If your kernel _is_ running in
> hypervisor mode, sc 1 does the same as sc 0, a normal system call.
>
> I don't know which it is for you; you didn't say.
>
> I have no idea what "a NULL call HSVC" means.  If you make exception c00
> return immediately (as you suggest) then you have made all system calls
> non-functional, which indeed is unlikely to work as you want.
>
>
> Segher

  reply	other threads:[~2018-10-08 16:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29 21:24 Looking for architecture papers Raz
2018-09-29 22:13 ` Segher Boessenkool
2018-09-30  7:05   ` Raz
2018-09-30  8:56     ` Segher Boessenkool
2018-10-03  4:07 ` Michael Ellerman
2018-10-04  7:41   ` Raz
2018-10-04  8:46     ` Segher Boessenkool
2018-10-04 10:16     ` Gabriel Paubert
2018-10-06  9:19       ` Raz
2018-10-06 12:27         ` Segher Boessenkool
2018-10-08 16:44           ` Raz [this message]
2018-10-08 19:29             ` Segher Boessenkool
2018-10-08 19:59     ` Gustavo Romero
2018-10-13  0:27       ` Raz

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='CAPB=Z-qC+Xgwyb=WAD-r_TYWWRRrpLJT6jFzCfKLtkNVn_FDUg@mail.gmail.com' \
    --to=raziebe@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=segher@kernel.crashing.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.