[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Keystone Issue


  • To: CodeWiz2280 <codewiz2280@xxxxxxxxx>
  • From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
  • Date: Fri, 5 Jun 2020 12:47:46 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mteM1wNltbXTw5kY/XIrXv2xFQSiYbFD/2Hznhk6rPY=; b=EsJWRhVKAcyCqM5dygUQTFD1sQM354LTmi5kigDrMn39v58f5hcFyTY7kzV8SfeBwlTeFgtDUDXo+xn8qcyhTFazDoVS0ejLp27iOVSfSfbCvayJXMgqC/tZGnaDWHabnmuSU3+Sj/jhaGXhAokPnRdD2g9x92LTetPz8Jl74NLhts7AOg4V/G6yGm0zvqoMUYf90ft9Aza/VKDiMcokwxAtSu6u0pWs9ohWWEineClNvBd/0/pVnSu0+NB9H9Lhm/75MpZOspMLr0AENNBc5xonOqj26czoiSQnGtntmKs68q7BzLiCSUtF9H5hwkZT4JH5oGNcTNrhesXkXZmzlQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MSmk2dKhLsCYElS9Bn4uLEwRd9u8iNz4xCtpODzblBe19kWWSRcQYeePNoP9nuApKreHtwZSoJZMAnSa5eurkTboADCFNeOl+PYnVv0aaCPm0Oiqljeh6+bgcJWX8ghZMUrsJwdOw39MGEpRHSrb1wF3F6zPWdqcWTdqmfSL+2wRWW6v/NsoiOYwf9TR3JGJzsiBdVYoZJ0HN+0dvkAFTTh/T7Rh6qQRTX6QuGBBqnXH7i+5NJLc8/xrPFzPFJ/V/Yl2opAWIbwmJ73+oRZZrv34Cx2s0kWqPBvNjg9Nf2Gd5KCoBVYq+6CPeA5OzXDXNKjvNg3mAozF99opIykUAA==
  • Authentication-results-original: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=arm.com;
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, nd <nd@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>
  • Delivery-date: Fri, 05 Jun 2020 12:48:00 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=arm.com;
  • Thread-index: AQHWOBaIAfEL/lLkK0WiNSn4kZcZc6jDwRQAgAAfVYCAACZwgIACvmKAgABfPYCAAA+JgIAA6NEAgAAP9wCAAAJxgIAAEuGAgAAfEwCAAGmFAIAAh2UAgABV34CAAFCtAIAAAUSAgAADZQCAAAGKgA==
  • Thread-topic: Keystone Issue


> On 5 Jun 2020, at 13:42, CodeWiz2280 <codewiz2280@xxxxxxxxx> wrote:
> 
> On Fri, Jun 5, 2020 at 8:30 AM Julien Grall <julien@xxxxxxx> wrote:
>> 
>> 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?
> Yes, that was a typo.  Sorry about that.  I meant that I am dumping
> /proc/interrupts and do not
> see them under the non-xen kernel or xen booted dom0.

Could you post both /proc/interrupts content ?

Cheers
Bertrand




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.