From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9A174C433DF for ; Fri, 5 Jun 2020 12:30:22 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 704422075B for ; Fri, 5 Jun 2020 12:30:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=xen.org header.i=@xen.org header.b="oolBT7qr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 704422075B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=xen.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jhBU9-0005M8-L4; Fri, 05 Jun 2020 12:30:09 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jhBU8-0005LI-Nq for xen-devel@lists.xenproject.org; Fri, 05 Jun 2020 12:30:08 +0000 X-Inumbo-ID: 4a879cc6-a728-11ea-afad-12813bfff9fa Received: from mail.xenproject.org (unknown [104.130.215.37]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 4a879cc6-a728-11ea-afad-12813bfff9fa; Fri, 05 Jun 2020 12:30:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=0JQ0JgUkd4aa0wYgbrQpBpjuIBYOmxVvjimtwAdDBx8=; b=oolBT7qrGJRr3LYa52ACtASyn9 sddyWdGl052N1nktcFyjfM9Vy83LXJxEVeQ4pVVpzfoRtRTQxSkWX1rxwtCuYrCEklu5txgbLRB5G xpU72nibw1RuFOi5N4WtjpPralDCIjJ7nNOlJ6gkNJet3ovZTi8jRn4mbAYVhmLdbK9Y=; Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1jhBU7-0004Zc-MW; Fri, 05 Jun 2020 12:30:07 +0000 Received: from [54.239.6.186] (helo=a483e7b01a66.ant.amazon.com) by xenbits.xenproject.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jhBU7-0001Q5-G6; Fri, 05 Jun 2020 12:30:07 +0000 Subject: Re: Keystone Issue To: CodeWiz2280 , Bertrand Marquis References: <25953300-f69d-19a4-9215-49cfedbd16ed@xen.org> <8C39F9D0-8351-4671-9A39-D5D4BFF02BD6@arm.com> <3ff17aa9-0aae-d598-40ce-4e90d4e50cc7@xen.org> <00E14EAD-BD23-4A3A-872E-0C47C26B7B41@arm.com> <8C6A23AE-6C2B-411F-ACAD-F5574211E8ED@arm.com> From: Julien Grall Message-ID: <14244e49-e1ac-a29d-bbd9-bd4c202bf186@xen.org> Date: Fri, 5 Jun 2020 13:30:05 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Cc: xen-devel , nd , Stefano Stabellini Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" 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