All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 PATCH 1/1] ARM64: KGDB: Add FP/SIMD debug support
Date: Fri, 28 Feb 2014 17:36:36 +0000	[thread overview]
Message-ID: <20140228173636.GG30996@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CALicx6v12DWQSqpP=pa_gJmyOqm4LmFHWc_9=n8Rt7M=krB+dQ@mail.gmail.com>

On Fri, Feb 28, 2014 at 11:08:58AM +0000, Vijay Kilari wrote:
> On Fri, Nov 29, 2013 at 3:27 PM, Vijay Kilari <vijay.kilari@gmail.com> wrote:
> >>> KGDB, being kernel debugger it was thought that allow
> >>> debugging only if kernel mode is supported.
> >>> In fact, I proposed (previous email)  to remove this condition and
> >>> allow to reading neon
> >>> registers always and allow write only if neon is in kernel mode.
> >>>
> >>
> >> I think KGDB is a special case here and should not considered as a
> >> user of kernel mode NEON. So even writing the registers should
> >> allowable regardless of this setting imo.
> >>
> 
>  Can we avoid checking on NEON state and allow debugger to
> access NEON registers irrespective of state to keep it simple?
> and just compile config is enough?

I'm afraid I don't follow... I think we *do* need to do the relevant
flush/sync operations, I just don't think it should be predicated on
KERNEL_MODE_NEON.

Will

  reply	other threads:[~2014-02-28 17:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 12:06 [RFC v2 PATCH 0/1] ARM64: KGDB: Add FPSIMD debug support vijay.kilari at gmail.com
2013-11-18 12:06 ` [RFC v2 PATCH 1/1] ARM64: KGDB: Add FP/SIMD " vijay.kilari at gmail.com
2013-11-25 18:52   ` Will Deacon
2013-11-25 19:03     ` Ard Biesheuvel
2013-11-26 11:57     ` Vijay Kilari
2013-11-29  8:53   ` Ard Biesheuvel
2013-11-29  9:20     ` Vijay Kilari
2013-11-29  9:27       ` Ard Biesheuvel
2013-11-29  9:57         ` Vijay Kilari
2014-02-28 11:08           ` Vijay Kilari
2014-02-28 17:36             ` Will Deacon [this message]
2014-03-02 13:08               ` Ard Biesheuvel
2014-03-03 11:43                 ` Will Deacon

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=20140228173636.GG30996@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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.