On Fri, Jul 7, 2017 at 2:53 PM, Chris Patterson wrote:
> On Fri, Jul 7, 2017 at 12:30 PM, Julien Grall wrote:
>> Hi Chris,
>>
>> On 07/07/17 00:12, Chris Patterson wrote:
>>>>
>>>>
>>>> So why do you want the hardware domain to interact w
On Fri, Jul 7, 2017 at 12:30 PM, Julien Grall wrote:
> Hi Chris,
>
> On 07/07/17 00:12, Chris Patterson wrote:
>>>
>>>
>>> So why do you want the hardware domain to interact with the ictlr? Could
>>> not
>>> you hide it completely?
>
On Fri, Jul 7, 2017 at 12:25 PM, Julien Grall wrote:
> Hi Chris,
>
>
> On 06/07/17 23:00, Chris Patterson wrote:
>>>>
>>>> The purpose of tegra_interrupt_compat is to maintain a tegra-specific
>>>> whitelist of interrupt controllers we know how
Will fix, thanks!
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
>
> So why do you want the hardware domain to interact with the ictlr? Could not
> you hide it completely?
>
snip
> What would happen if you enable the interrupt here for the guest? Should not
> you do it when the guest is requesting to enable (see vgic_enable_irqs).
>
>
> Also, how about EOI an
>> The purpose of tegra_interrupt_compat is to maintain a tegra-specific
>> whitelist of interrupt controllers we know how to route. Presumably,
>> there may be custom boards out there that may have additional
>> interrupt routing capabilities that this patch set would not support
>> as-is. I'm n
Will split patches & fix for v2, thanks!
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
>> +static const char * const tegra_dt_compat[] __initconst =
>> +{
>> +"nvidia,tegra120", /* Tegra K1 */
>
> This is still tegra120 (not tegra124), is that intended? If so, it is
> still missing from arch/arm*/boot/dts. Do you have a pointer?
It was not intended; thank you for catching it. I
From: Chris Patterson
Several Tegra hardware devices, and the Tegra device tree, expect
the presence of a Tegra Legacy Interrupt Controller (LIC) in the hardware
domain. Accordingly, we'll need to expose (most of) the LIC's registers
to the hardware domain.
As the Tegra LIC provides t
From: Chris Patterson
Tegra boards feature a NS16550-compatible serial mapped into the MMIO
space. Add support for its use both as a full-featured serial port and
as an earlyprintk driver.
This patch adds a quirk for platforms, such as the Tegra, which require
require the NS16550 Rx timeout
From: "Chris Patterson"
Some common platforms (e.g. Tegra) have non-traditional IRQ controllers
that must be programmed in addition to their primary GICs-- and which
can come in unusual topologies. Device trees for targets that feature
these controllers often deviate from the conven
m the original RFC
posted by Kyle Temkin. Kyle has done most of the authoring on this, but I am
picking it up to address the RFC reviews and push it though.
Chris Patterson (6):
xen/arm: platforms: Add earlyprintk and serial support for Tegra
boards.
xen/arm: domain_build: Inherit GIC's
From: "Chris Patterson"
Tegra devices have a legacy interrupt controller (lic, or ictlr) that
must be programmed in parallel with their primary GIC. For all intents
and purposes, we treat these devices attached to this controller as
connected to the primary GIC, as it will be hand
From: "Chris Patterson"
The addition of new IRQ-related platform hooks now allow platforms to
perform platform-specific interrupt logic, such as allowing virtualization
of platform-specific interrupt controller hardware.
This commit adds the ability for the platform to identify th
From: "Chris Patterson"
Currently, the interrupt parent is left undefined during creation in
make_gic_node(). In cases where a non-GIC interrupt controller is present,
this can lead to incorrect assignment of interrupt parents.
On the Tegra, the gic's interrupt parent i
> I would suggest to start with a 1 hour meeting on the Wednesday 23rd
> November. I know that people are spread across different timezones, so I
> would like to gather thought before choosing a time.
>
Sounds good! EST (GMT-5).
Cheers,
-Chris
___
Xen-
On Wed, Sep 21, 2016 at 10:07 AM, Konrad Rzeszutek Wilk
wrote:
> On Wed, Sep 21, 2016 at 09:50:30AM -0400, Chris Patterson wrote:
>> On Wed, Sep 21, 2016 at 9:00 AM, Wei Liu wrote:
>> > On Wed, Sep 21, 2016 at 08:51:07AM -0400, Konrad Rzeszutek Wilk wrote:
>> >>
On Wed, Sep 21, 2016 at 9:00 AM, Wei Liu wrote:
> On Wed, Sep 21, 2016 at 08:51:07AM -0400, Konrad Rzeszutek Wilk wrote:
>> On Tue, Sep 20, 2016 at 05:29:39PM -0400, Chris Patterson wrote:
>> > From: Chris Patterson
>> >
>> > xs_watch() creates a thread to l
From: Chris Patterson
xs_watch() creates a thread to listen to xenstore events. Currently, the
thread is created with the greater of 16K or PTHREAD_MIN_SIZE.
There have been several bug reports and workarounds related to the issue
where xs_watch() fails because its attempt to create the reader
I have spent some time investigating a case where qemu is failing to
register xenstore watches for a PV guest once I enable vfb (and
thereby triggering the creation of a qemu instance).
The qemu logs show something along the lines of:
xen be core: xen be core: xen be: watching backend path
(backen
From: Chris Patterson
The uart generates an interrupt whenever the transmit holding register is
empty and UART_IER_ETHREI is set in UART_IER. Currently, Xen's ns16550
driver does not currently mask this interrupt when transmit is stopped,
unlike other platforms such as Linux [1].
T
On Wed, Aug 17, 2016 at 10:29 AM, Jan Beulich wrote:
>>>> On 17.08.16 at 16:02, wrote:
>> From: Chris Patterson
>>
>> The uart generates an interrupt whenever the transmit holding register is
>> empty and UART_IER_ETHREI is set in UART_IER. Currently, Xen&#x
From: Chris Patterson
The uart generates an interrupt whenever the transmit holding register is
empty and UART_IER_ETHREI is set in UART_IER. Currently, Xen's ns16550
driver does not currently mask this interrupt when transmit is stopped,
unlike other platforms such as Linux [1].
T
From: Chris Patterson
GCC 6 will warn on unused static const variables in c modules:
https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00847.html
When compiling with LIBXL_HAVE_NO_SUSPEND_RESUME set (arm & aarch64),
the compiler emits the following errors:
xl_cmdimpl.c:101:19: e
From: Chris Patterson
Replace the usage of readdir_r() with readdir() to address a
compilation error under glibc due to the deprecation of readdir_r
for their next release (2.24) [1, 2].
Remove code specific to usage of readdir_r which is no longer required,
such as zalloc_dirent().
--
From
From: Chris Patterson
Replace the usage of readdir_r() with readdir() to address a
compilation error under glibc due to the deprecation of readdir_r
for their next release (2.24) [1, 2].
Add new error checking on readdir(), and fail if error occurs.
--
From the GNU libc manual [3]:
"
On Thu, Jun 2, 2016 at 12:13 PM, Ian Jackson wrote:
> Chris Patterson writes ("Re: [[PATCH v2 2/2] libxl: replace deprecated
> readdir_r() with readdir()"):
>> You're right, it should check for the error afterwards.
>>
>> How about something along the
On Thu, Jun 2, 2016 at 6:11 AM, Ian Jackson wrote:
> Chris Patterson writes ("[[PATCH v2 2/2] libxl: replace deprecated
> readdir_r() with readdir()"):
>> -for (;;) {
>> +while ((de = readdir(dir)) != NULL) {
> ...
>> -int r = readdir_r
From: Chris Patterson
Replace the usage of readdir_r() with readdir() to address a
compilation error under glibc due to the deprecation of readdir_r
for their next release (2.24) [1, 2].
--
From the GNU libc manual [3]:
"
It is expected that future versions of POSIX will obsolete read
From: Chris Patterson
Replace the usage of readdir_r() with readdir() to address a
compilation error under glibc due to the deprecation of readdir_r
for their next release (2.24) [1, 2].
Remove code specific to usage of readdir_r which is no longer required,
such as zalloc_dirent().
--
From
On Wed, Jun 1, 2016 at 8:06 AM, Ian Jackson wrote:
> Ian Jackson writes ("Re: [Xen-devel] [PATCH 1/2] libfsimage: replace
> deprecated readdir_r() with readdir()"):
>> Ian Jackson writes ("Re: [Xen-devel] [PATCH 1/2] libfsimage: replace
>> deprecated readdir_r() with readdir()"):
>> > 2. There m
On Tue, May 31, 2016 at 1:53 PM, Wei Liu wrote:
> On Tue, May 31, 2016 at 11:43:13AM -0400, Chris Patterson wrote:
>> On Tue, May 31, 2016 at 6:42 AM, George Dunlap
>> wrote:
>> > On Mon, May 30, 2016 at 3:32 AM, Chris Patterson wrote:
>> >> From: Chris Patt
On Tue, May 31, 2016 at 6:42 AM, George Dunlap wrote:
> On Mon, May 30, 2016 at 3:32 AM, Chris Patterson wrote:
>> From: Chris Patterson
>>
>> Replace the usage of readdir_r() with readdir() to address
>> a compilation error due to the deprecation of readdir_r.
>
From: Chris Patterson
In some cross-compilation environments, the CC/CXX variables may
expand out to more than one argument (to include things
like --sysroot=...). Quote these to safely pass along.
Signed-off-by: Chris Patterson
---
xen/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3
From: Chris Patterson
Replace the usage of readdir_r() with readdir() to address
a compilation error due to the deprecation of readdir_r.
glibc has deprecated this for their next release (2.24):
https://sourceware.org/bugzilla/show_bug.cgi?id=19056
This also removes the zalloc_dirent() helper
From: Chris Patterson
Replace the usage of readdir_r() with readdir() to address
a compilation error due to the deprecation of readdir_r.
glibc has deprecated this for their next release (2.24):
https://sourceware.org/bugzilla/show_bug.cgi?id=19056
Signed-off-by: Chris Patterson
---
tools
On Tue, May 17, 2016 at 9:37 AM, Konrad Rzeszutek Wilk
wrote:
>> - The serial controller on the Tegra SoCs doesn't behave in the same
>> was as most NS16550-compatibles; it actually adheres to the NS16550
>> spec a little more rigidly than most compatible controller
On Tue, Apr 5, 2016 at 12:42 PM, Konrad Rzeszutek Wilk
wrote:
> On Tue, Apr 05, 2016 at 11:43:36AM -0400, Chris Patterson wrote:
>> On Tue, Apr 5, 2016 at 9:49 AM, Konrad Rzeszutek Wilk
>> wrote:
>> > On Mon, Apr 04, 2016 at 10:48:11PM -0400, Chris Patterson wrote:
&g
On Tue, Apr 5, 2016 at 9:49 AM, Konrad Rzeszutek Wilk
wrote:
> On Mon, Apr 04, 2016 at 10:48:11PM -0400, Chris Patterson wrote:
>> Add earlycon=xenboot option to Documentation/kernel-parameters.txt.
>>
>
> But it is not true.
>
> I tried this on x86: "earlyco
Add earlycon=xenboot option to Documentation/kernel-parameters.txt.
Signed-off-by: Chris Patterson
---
Documentation/kernel-parameters.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/kernel-parameters.txt
b/Documentation/kernel-parameters.txt
index ecc74fa..e01ec39
40 matches
Mail list logo
