All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
	stefano.stabellini@citrix.com
Subject: Re: [PATCH 3/4] xen/arm: Implement a dummy debug monitor for ARM32
Date: Fri, 02 May 2014 15:22:27 +0100	[thread overview]
Message-ID: <5363AA23.4010901@linaro.org> (raw)
In-Reply-To: <1399040328.6043.41.camel@kazak.uk.xensource.com>

On 05/02/2014 03:18 PM, Ian Campbell wrote:
> On Fri, 2014-05-02 at 14:39 +0100, Julien Grall wrote:
>> On 05/02/2014 02:26 PM, Ian Campbell wrote:
>>> On Fri, 2014-05-02 at 13:53 +0100, Julien Grall wrote:
>>>> I don't plan to more spend time to write a correct emulation (i.e
>>>> context switching) to support HW debug.
>>>
>>> I'm not going to ack a patch which causes arm32 to diverge from arm64 in
>>> this area, especially not when the correct solution (more critical on
>>> arm64 than arm32) is to properly context switch these registers.
>>
>> We don't diverge... The Linux HW debug arm32 implementation doesn't
>> permit to use RAZ/WI on some registers.
>>
>> Currently arm64 HW debug may or may not work but it won't crash the
>> guest. It's not the case on arm32. So the current Xen already diverge.
> 
> I think that was a mistake (albeit made under the pressure of a security
> embargo), we shouldn't diverge further.
> 
>> As said earlier, the HW debug is not essential. Writing a proper
>> emulation will take some time and I don't have time for writing and
>> testing it correctly.
> 
> This is not about writing any sort of emulation AFAICT. It is about
> context switching a couple of dozen new registers, of which 80% are
> multiple instances of the same type of register.
> 
> The proper solution won't involve any trapping at all. (Maybe we will do
> lazy context switching at some point, but that's another thing).

Are we sure that context switching won't lead to another security issue?
It's not clear to me how debugging behave with virtualization.

-- 
Julien Grall

  reply	other threads:[~2014-05-02 14:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 22:45 [PATCH 0/4] xen/arm32: Follow-up XSA-93 Julien Grall
2014-04-24 22:45 ` [PATCH 1/4] xen/arm: Add missing newline after commit 60f7376 Julien Grall
2014-05-02 12:58   ` Ian Campbell
2014-05-02 12:59     ` Julien Grall
2014-04-24 22:45 ` [PATCH 2/4] xen/arm: Implement a dummy Performance Monitor for ARM32 Julien Grall
2014-05-02 11:01   ` Ian Campbell
2014-05-02 12:41     ` Julien Grall
2014-06-13 12:02       ` Ian Campbell
2014-04-24 22:45 ` [PATCH 3/4] xen/arm: Implement a dummy debug monitor " Julien Grall
2014-05-02 11:09   ` Ian Campbell
2014-05-02 12:53     ` Julien Grall
2014-05-02 13:14       ` Ian Campbell
2014-05-02 13:29         ` Julien Grall
2014-06-13 12:02           ` Ian Campbell
2014-06-14 17:16             ` Julien Grall
2014-05-02 13:26       ` Ian Campbell
2014-05-02 13:39         ` Julien Grall
2014-05-02 14:18           ` Ian Campbell
2014-05-02 14:22             ` Julien Grall [this message]
2014-05-02 15:17               ` Ian Campbell
2014-04-24 22:45 ` [PATCH 4/4] xen/arm: Add some useful debug in coprocessor trapping Julien Grall
2014-05-02 11:12   ` Ian Campbell
2014-05-02 12:58     ` Julien Grall

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=5363AA23.4010901@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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.