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=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 5214FC433E0 for ; Tue, 19 Jan 2021 07:56:11 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (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 D1E3D230FE for ; Tue, 19 Jan 2021 07:56:10 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D1E3D230FE Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kroah.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94) (envelope-from ) id 1l1lrm-0007e2-6A; Tue, 19 Jan 2021 02:55:54 -0500 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1l1lrj-0007du-Pk for kernelnewbies@kernelnewbies.org; Tue, 19 Jan 2021 02:55:52 -0500 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id EAEE45C0198; Tue, 19 Jan 2021 02:55:48 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 19 Jan 2021 02:55:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=U5AlJGNPwoE5/dxKE7z8AD5jE17 OZ7Z26Q8UWZkgydI=; b=ZvMcZYwYKv+j55fHE2KgI8BRsgHU+jjkpdTvEelO01e ZSoK8CaZrs+MLvK6SdMjLYgfxlwo8HNocrooovgRrL3/H6slzlA6SBK2L2qQnKBk ZUib2/UL04xjiv544eFLi1hT4QR3vrgpK7n24I3kqy+ZBeKltCBxItpduu7X0x3v vzLPqEWxI01nyvsp+WdveZKjtf4AR071vYyt54pdDguezmYVALEoh7eMWxeVFvBf 5tvIVI9GokGfcEa7mNDVU04dVW1AeSl1NaMIKr4SuFOghmBHmzanxVnGKrN3yX7K Loh01A7vPDViB1lwczoweBQDtYifRgVvL2ZgCVqYoEQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=U5AlJG NPwoE5/dxKE7z8AD5jE17OZ7Z26Q8UWZkgydI=; b=Nq6J0tAtXrfs7qKL26Hf3m 5CRO6aXOYysZ5pOfE1Gwu0LEo5LPMBSmm5D2Rt46b5op9gKmwIjMcaHmoHHaiKIH 1xXOwvcRd8Z6/okoWOHXQNL88HP8DtDSngiNJTBsl+l1dIGJy4Nq/X1p0izkJYp9 zSrygLz0u3D2FED/Ldc02cyG/9GxBIg1FqmT9jnix34VCLIbhHPOLeFdlAQaH9tN wd05J+kfICVlhYJLnXtlUOh83UDXEz5YlOvEtLM/6nnJ2BNEJ/3ccrRuMvjl7uGD 9yU262AYviYVjT3Vu6A2iOGpcevNL8aMR2/GwbgfZ030v7nXyaYYsh/Oy4siOcVw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrtdelgdduuddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepifhrvghgucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheq necuggftrfgrthhtvghrnhepveeuheejgfffgfeivddukedvkedtleelleeghfeljeeiue eggeevueduudekvdetnecukfhppeekfedrkeeirdejgedrieegnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrdgtoh hm X-ME-Proxy: Received: from localhost (83-86-74-64.cable.dynamic.v4.ziggo.nl [83.86.74.64]) by mail.messagingengine.com (Postfix) with ESMTPA id 75E9C108005F; Tue, 19 Jan 2021 02:55:48 -0500 (EST) Date: Tue, 19 Jan 2021 08:55:47 +0100 From: Greg KH To: Pankaj Vinodrao Joshi Subject: Re: /proc/cpuinfo not showing all info Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: "kernelnewbies@kernelnewbies.org" X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Tue, Jan 19, 2021 at 07:38:13AM +0000, Pankaj Vinodrao Joshi wrote: > i agree each processor type exports different information but i need to pop up information while i do /proc/cpu also i have observed that almost every arch display information w.r.t frequency. Can you suggest how i can add info related to cpufreq into /proc ? I am sorry, but I can not parse this very well, can you please explain exactly what you wish to do and why the "normal" apis that expose the current frequency of the processor do not work for you? (hint, it's not /proc/cpuinfo) Also, who is demanding this requirement? thanks, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies