linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Raz <raziebe@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Looking for architecture papers
Date: Sat, 6 Oct 2018 07:27:50 -0500	[thread overview]
Message-ID: <20181006122750.GF29268@gate.crashing.org> (raw)
In-Reply-To: <CAPB=Z-pW6FWEp=0PgphCo-mAh9pPgt0frjz_MkPp6YHuhX3-pQ@mail.gmail.com>

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-06 12:30 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 [this message]
2018-10-08 16:44           ` Raz
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=20181006122750.GF29268@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=raziebe@gmail.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).