All of lore.kernel.org
 help / color / mirror / Atom feed
From: gaosong <gaosong@loongson.cn>
To: Richard Henderson <richard.henderson@linaro.org>,
	maobibo <maobibo@loongson.cn>,
	qemu-devel@nongnu.org
Cc: laurent@vivier.eu, Xiaojuan Yang <yangxiaojuan@loongson.cn>
Subject: Re: [PATCH v19 02/13] linux-user: Add LoongArch signal support
Date: Fri, 24 Jun 2022 09:41:40 +0800	[thread overview]
Message-ID: <154da18c-5a57-e153-1ca3-0653e3c9eea0@loongson.cn> (raw)
In-Reply-To: <7fbda1a0-938d-fe5d-a6e7-ddaef3577555@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]


On 2022/6/24 上午9:20, Richard Henderson wrote:
> On 6/23/22 17:45, maobibo wrote:
>>
>>
>> 在 2022/6/24 07:34, Richard Henderson 写道:
>>> On 6/23/22 01:55, Song Gao wrote:
>>>> +static void setup_sigcontext(CPULoongArchState *env,
>>>> +                             struct target_sigcontext *sc,
>>>> +                             struct extctx_layout *extctx)
>>>> +{
>>>> +    int i;
>>>> +
>>>> +    if (extctx->flags & SC_USED_FP) {
>>>> +        __put_user(extctx->fpu.addr, &sc->sc_extcontext[0]);
>>>> +    } else {
>>>> +        __put_user(extctx->end.addr, &sc->sc_extcontext[0]);
>>>> +    }
>>>
>>> This is incorrect.  Where did this come from?  It certainly doesn't 
>>> appear in the kernel's version of setup_sigcontext. The only reason 
>>> the result works for you is that this is overwritten by 
>>> copy_fpu_to_sigframe within setup_sigframe.
>>
>> The val of flags is SC_USED_FP alway in function setup_extcontext in 
>> this version. We want to optimization in future if FP is not used for 
>> application where sigcontext for FP is not necessary. Also it can 
>> will be extended for 128bit/256bit vector FPU.
>
> No, that's not what I mean.  The store of the address is incorrect.
> This is no such address stored in the frame at this location.
>
> If you believe that I am incorrect, please point to the line within 
> the kernel source to which this corresponds.

You're right,   I'll corrrect on next version.

Thanks.
Song Gao

[-- Attachment #2: Type: text/html, Size: 2668 bytes --]

  reply	other threads:[~2022-06-24  1:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  8:55 [PATCH v19 00/13] Add LoongArch linux-user emulation support Song Gao
2022-06-23  8:55 ` [PATCH v19 01/13] linux-user: Add LoongArch generic header files Song Gao
2022-06-23  8:55 ` [PATCH v19 02/13] linux-user: Add LoongArch signal support Song Gao
2022-06-23 23:34   ` Richard Henderson
2022-06-24  0:45     ` maobibo
2022-06-24  1:13       ` maobibo
2022-06-24  1:20       ` Richard Henderson
2022-06-24  1:41         ` gaosong [this message]
2022-06-23  8:55 ` [PATCH v19 03/13] linux-user: Add LoongArch elf support Song Gao
2022-06-23  8:55 ` [PATCH v19 04/13] linux-user: Add LoongArch syscall support Song Gao
2022-06-23  8:55 ` [PATCH v19 05/13] linux-user: Add LoongArch cpu_loop support Song Gao
2022-06-23  8:55 ` [PATCH v19 06/13] scripts: add loongarch64 binfmt config Song Gao
2022-06-23  8:55 ` [PATCH v19 07/13] target/loongarch: remove badaddr from CPULoongArch Song Gao
2022-06-23  8:55 ` [PATCH v19 08/13] target/loongarch: Fix missing update CSR_BADV Song Gao
2022-06-23  8:55 ` [PATCH v19 09/13] target/loongarch: Fix helper_asrtle_d/asrtgt_d raise wrong exception Song Gao
2022-06-23  8:55 ` [PATCH v19 10/13] target/loongarch: remove unused include hw/loader.h Song Gao
2022-06-23  8:55 ` [PATCH v19 11/13] target/loongarch: Adjust functions and structure to support user-mode Song Gao
2022-06-23  8:55 ` [PATCH v19 12/13] default-configs: Add loongarch linux-user support Song Gao
2022-06-23  8:55 ` [PATCH v19 13/13] target/loongarch: Update README Song Gao

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=154da18c-5a57-e153-1ca3-0653e3c9eea0@loongson.cn \
    --to=gaosong@loongson.cn \
    --cc=laurent@vivier.eu \
    --cc=maobibo@loongson.cn \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=yangxiaojuan@loongson.cn \
    /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.