From: Julien Grall <julien@xen.org>
To: CodeWiz2280 <codewiz2280@gmail.com>,
Bertrand Marquis <Bertrand.Marquis@arm.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, nd <nd@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: Keystone Issue
Date: Fri, 5 Jun 2020 13:30:05 +0100 [thread overview]
Message-ID: <14244e49-e1ac-a29d-bbd9-bd4c202bf186@xen.org> (raw)
In-Reply-To: <CALYbLDiOX0JW_=6AgAb+m5q++3WvQtivJRy+ePrp5pJXd7T9Vg@mail.gmail.com>
Hi,
On 05/06/2020 13:25, CodeWiz2280 wrote:
> The Keystone uses the netcp driver, which has interrupts from 40-79
> listed in the device tree (arch/arm/boot/keystone-k2e-netcp.dtsi).
> I'm using the same device tree between my non-xen standalone kernel
> and my dom0 kernel booted by xen. In the standalone (non-xen) kernel
> the ethernet works fine, but I don't see any of its interrupts in the
> output of /proc/iomem. I'm not seeing them in /proc/iomem when
> running dom0 under Xen either. When booting with Xen I get this
> behavior where the ifconfig output shows 1 RX message and 1 TX
> message, and then nothing else.
I am not sure whether this is a typo in the e-mail. /proc/iomem is
listing the list of the MMIO regions. You want to use /proc/interrupts.
Can you confirm which path you are dumping?
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2020-06-05 12:30 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 12:38 Keystone Issue CodeWiz2280
2020-06-01 13:29 ` Julien Grall
2020-06-01 15:21 ` CodeWiz2280
2020-06-01 17:38 ` CodeWiz2280
2020-06-03 11:32 ` Julien Grall
2020-06-03 17:13 ` CodeWiz2280
2020-06-03 18:09 ` Julien Grall
2020-06-03 18:37 ` CodeWiz2280
2020-06-04 8:02 ` Bertrand Marquis
2020-06-04 8:59 ` Julien Grall
2020-06-04 9:08 ` Bertrand Marquis
2020-06-04 10:15 ` Julien Grall
2020-06-04 12:07 ` CodeWiz2280
2020-06-04 18:24 ` Julien Grall
2020-06-05 2:29 ` CodeWiz2280
2020-06-05 7:36 ` Bertrand Marquis
2020-06-05 12:25 ` CodeWiz2280
2020-06-05 12:30 ` Julien Grall [this message]
2020-06-05 12:42 ` CodeWiz2280
2020-06-05 12:47 ` Bertrand Marquis
2020-06-05 15:05 ` CodeWiz2280
2020-06-05 19:12 ` CodeWiz2280
2020-06-08 8:40 ` Bertrand Marquis
2020-06-08 12:33 ` CodeWiz2280
2020-06-08 16:13 ` Stefano Stabellini
2020-06-09 14:33 ` CodeWiz2280
2020-06-09 15:28 ` Bertrand Marquis
2020-06-09 15:47 ` Julien Grall
2020-06-09 15:58 ` CodeWiz2280
2020-06-09 17:05 ` Bertrand Marquis
2020-06-09 17:03 ` Bertrand Marquis
2020-06-09 17:32 ` Julien Grall
2020-06-09 17:45 ` Marc Zyngier
2020-06-09 20:07 ` CodeWiz2280
2020-06-10 8:13 ` Bertrand Marquis
2020-06-10 8:06 ` Bertrand Marquis
2020-06-10 8:20 ` Marc Zyngier
2020-06-10 8:39 ` Bertrand Marquis
2020-06-10 12:39 ` CodeWiz2280
2020-06-10 12:53 ` Marc Zyngier
2020-06-10 12:58 ` Julien Grall
2020-06-10 21:46 ` Julien Grall
2020-06-15 19:14 ` CodeWiz2280
2020-06-15 21:32 ` Stefano Stabellini
2020-06-16 7:56 ` Bertrand Marquis
2020-06-16 8:11 ` Marc Zyngier
2020-06-16 18:13 ` CodeWiz2280
2020-06-16 18:23 ` Marc Zyngier
2020-06-17 14:45 ` CodeWiz2280
2020-06-17 15:25 ` Marc Zyngier
2020-06-17 18:46 ` Stefano Stabellini
2020-06-17 23:52 ` CodeWiz2280
2020-06-23 20:50 ` CodeWiz2280
2020-06-24 7:50 ` Bertrand Marquis
2020-06-24 17:28 ` Stefano Stabellini
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=14244e49-e1ac-a29d-bbd9-bd4c202bf186@xen.org \
--to=julien@xen.org \
--cc=Bertrand.Marquis@arm.com \
--cc=codewiz2280@gmail.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.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.