From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: TTY: hvc_dcc: Add support for ARM64 dcc
Date: Tue, 17 Jun 2014 10:51:56 +0100 [thread overview]
Message-ID: <20140617095155.GD13020@arm.com> (raw)
In-Reply-To: <1402957778-13830-1-git-send-email-abhimany@codeaurora.org>
On Mon, Jun 16, 2014 at 11:29:38PM +0100, Abhimanyu Kapur wrote:
> Add support for debug communications channel based
> hvc console for arm64 cpus.
Should we be setting MDSCR_EL1.TDCC to prevent userspace access to the DCC?
> Signed-off-by: Abhimanyu Kapur <abhimany@codeaurora.org>
> ---
> arch/arm64/include/asm/dcc.h | 41 +++++++++++++++++++++++++++++++++++++++++
> drivers/tty/hvc/Kconfig | 2 +-
> 2 files changed, 42 insertions(+), 1 deletion(-)
> create mode 100644 arch/arm64/include/asm/dcc.h
>
> diff --git a/arch/arm64/include/asm/dcc.h b/arch/arm64/include/asm/dcc.h
> new file mode 100644
> index 0000000..ef74324
> --- /dev/null
> +++ b/arch/arm64/include/asm/dcc.h
> @@ -0,0 +1,41 @@
> +/* Copyright (c) 2014 The Linux Foundation. All rights reserved.
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 and
> + * only version 2 as published by the Free Software Foundation.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + * GNU General Public License for more details.
> + */
> +
> +#include <asm/barrier.h>
> +
> +static inline u32 __dcc_getstatus(void)
> +{
> + u32 __ret;
Can this result in the mrs receiving a W register?
> + asm volatile("mrs %0, mdccsr_el0" : "=r" (__ret)
> + : : "cc");
Why the CC clobber? Why volatile?
> +
> + return __ret;
> +}
> +
> +static inline char __dcc_getchar(void)
> +{
> + char __c;
> +
> + asm volatile("mrs %0, dbgdtrrx_el0" : "=r" (__c));
> + isb();
Why the isb and why volatile??
> +
> + return __c;
> +}
> +
> +static inline void __dcc_putchar(char c)
> +{
> + asm volatile("msr dbgdtrtx_el0, %0"
> + : /* No output register */
> + : "r" (c));
Can you guarantee that GCC hasn't put junk in the upper bits of c?
> + isb();
Why the isb?
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Abhimanyu Kapur <abhimany@codeaurora.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>
Subject: Re: [PATCH] ARM64: TTY: hvc_dcc: Add support for ARM64 dcc
Date: Tue, 17 Jun 2014 10:51:56 +0100 [thread overview]
Message-ID: <20140617095155.GD13020@arm.com> (raw)
In-Reply-To: <1402957778-13830-1-git-send-email-abhimany@codeaurora.org>
On Mon, Jun 16, 2014 at 11:29:38PM +0100, Abhimanyu Kapur wrote:
> Add support for debug communications channel based
> hvc console for arm64 cpus.
Should we be setting MDSCR_EL1.TDCC to prevent userspace access to the DCC?
> Signed-off-by: Abhimanyu Kapur <abhimany@codeaurora.org>
> ---
> arch/arm64/include/asm/dcc.h | 41 +++++++++++++++++++++++++++++++++++++++++
> drivers/tty/hvc/Kconfig | 2 +-
> 2 files changed, 42 insertions(+), 1 deletion(-)
> create mode 100644 arch/arm64/include/asm/dcc.h
>
> diff --git a/arch/arm64/include/asm/dcc.h b/arch/arm64/include/asm/dcc.h
> new file mode 100644
> index 0000000..ef74324
> --- /dev/null
> +++ b/arch/arm64/include/asm/dcc.h
> @@ -0,0 +1,41 @@
> +/* Copyright (c) 2014 The Linux Foundation. All rights reserved.
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 and
> + * only version 2 as published by the Free Software Foundation.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + * GNU General Public License for more details.
> + */
> +
> +#include <asm/barrier.h>
> +
> +static inline u32 __dcc_getstatus(void)
> +{
> + u32 __ret;
Can this result in the mrs receiving a W register?
> + asm volatile("mrs %0, mdccsr_el0" : "=r" (__ret)
> + : : "cc");
Why the CC clobber? Why volatile?
> +
> + return __ret;
> +}
> +
> +static inline char __dcc_getchar(void)
> +{
> + char __c;
> +
> + asm volatile("mrs %0, dbgdtrrx_el0" : "=r" (__c));
> + isb();
Why the isb and why volatile??
> +
> + return __c;
> +}
> +
> +static inline void __dcc_putchar(char c)
> +{
> + asm volatile("msr dbgdtrtx_el0, %0"
> + : /* No output register */
> + : "r" (c));
Can you guarantee that GCC hasn't put junk in the upper bits of c?
> + isb();
Why the isb?
Will
next prev parent reply other threads:[~2014-06-17 9:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 22:29 [PATCH] ARM64: TTY: hvc_dcc: Add support for ARM64 dcc Abhimanyu Kapur
2014-06-16 22:29 ` Abhimanyu Kapur
2014-06-17 9:51 ` Will Deacon [this message]
2014-06-17 9:51 ` Will Deacon
2015-06-05 18:35 ` Timur Tabi
2015-06-05 18:35 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2015-06-19 22:08 Timur Tabi
2015-06-19 22:08 ` Timur Tabi
2015-06-22 13:12 ` Will Deacon
2015-06-22 13:12 ` Will Deacon
2015-06-22 13:16 ` Timur Tabi
2015-06-22 13:16 ` Timur Tabi
2015-06-24 20:11 ` Timur Tabi
2015-06-24 20:11 ` Timur Tabi
2015-06-30 13:51 ` Will Deacon
2015-06-30 13:51 ` Will Deacon
2015-06-30 13:58 ` Timur Tabi
2015-06-30 13:58 ` Timur Tabi
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=20140617095155.GD13020@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.