qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>, qemu-s390x@nongnu.org
Cc: thuth@redhat.com, david@redhat.com, cohuck@redhat.com,
	qemu-devel@nongnu.org, borntraeger@de.ibm.com,
	mihajlov@linux.ibm.com
Subject: Re: [PATCH v1 0/1] s390x: protvirt: SCLP interpretation
Date: Thu, 28 Nov 2019 14:15:12 +0100	[thread overview]
Message-ID: <d1cf8a77-1956-1226-fdf2-715524f7f0f7@linux.ibm.com> (raw)
In-Reply-To: <7f2202c7-b9ed-d1c8-7b5c-e6b8871aa931@linux.ibm.com>


On 2019-11-28 13:28, Janosch Frank wrote:
> On 11/28/19 11:13 AM, Pierre Morel wrote:
>> A new proposition:
>> I think it would be wise to fork directly from handle_instruction
>> instead to accept per default all instructions with with secure
>> instruction interception code.
>> Just in case future firmware with older QEMU.
>>
>> How ever I let three dors open.
>>
>> 1) This patch accepts the all B2 instructions, mostly I/O.
>> Some of the instructions will not work correctly for PV until patched.
>> This should be fixed, and will be, in a separate patch.
>>
>> 2) The same is true for DIAG instructions.
>>
>> 3) Secure notifications are separated from secure instructions and
>> normal instructions interception because this case is completely new.
>> For B2 instructions we do not have to do anything this just informative.
>> However, one information is of interrest, a notification that
>> SIGP(STOP) is sent to stop the CPUs and terminate QEMU.
> Pierre, I told you this morning that I don't want this and that you
> should leave this untouched until I can explain my thoughts behind the
> initial patch in a f2f.
> Thomas' review of your change only confirmed my concerns about this patch.
>
> This is the wrong patch at the wrong time, which creates noise and work
> for other people. Please stop and work on something else.

!?

- you sent to me info on slack that I did not see until now, next time 
be sure I have acknowledged if it is important.

- You told me to dive into this patch quite abruptly, and it invested 
time to understand how the I/O works with PV, so sorry for the wrong time

- I see no problem with the questions from Thomas, may be you can 
explain this to me

- I have a lot of other things to do so I just close this thread after 
having answered to Thomas.


>
>
>
>>
>>
>> Pierre Morel (1):
>>    s390x: protvirt: SCLP interpretation
>>
>>   hw/s390x/sclp.c         | 18 +++++++++++++
>>   include/hw/s390x/sclp.h |  2 ++
>>   target/s390x/kvm.c      | 56 ++++++++++++++++++++++++++++++++++++++++-
>>   3 files changed, 75 insertions(+), 1 deletion(-)
>>
>
-- 
Pierre Morel
IBM Lab Boeblingen



  reply	other threads:[~2019-11-28 13:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 10:13 [PATCH v1 0/1] s390x: protvirt: SCLP interpretation Pierre Morel
2019-11-28 10:13 ` [PATCH v1 1/1] " Pierre Morel
2019-11-28 12:10   ` Thomas Huth
2019-11-28 13:05     ` Pierre Morel
2019-11-28 12:28 ` [PATCH v1 0/1] " Janosch Frank
2019-11-28 13:15   ` Pierre Morel [this message]
2019-11-28 23:09 ` no-reply

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=d1cf8a77-1956-1226-fdf2-715524f7f0f7@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=mihajlov@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.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).