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=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED 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 C3211C43331 for ; Thu, 2 Apr 2020 12:20:22 +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 81DE2206F8 for ; Thu, 2 Apr 2020 12:20:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="I6buHts5"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="KbtJLwsZ" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 81DE2206F8 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.92.3) (envelope-from ) id 1jJyp3-0000Dg-SP; Thu, 02 Apr 2020 08:19:49 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jJyp1-0000Da-HR for kernelnewbies@kernelnewbies.org; Thu, 02 Apr 2020 08:19:47 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id ACEFD5C029E; Thu, 2 Apr 2020 08:19:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 02 Apr 2020 08:19:46 -0400 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=fm3; bh=spV61mG0jRUhZzYytTyhEn+ihN3 DsNBNuzcLNwI8qDg=; b=I6buHts5yRFGePjK+mRPwhTMkwOmvMWTmcffqdkty18 8ZW3QaQPwenraV0e+Il22IRQVgpKsFIcPFSvFcgUdvCmN2H4fpqCSHnN0KetHmtH 5ZNBuOfrC/zw6lrAUV1R4GMmAltjMJoeGuFH96sOFrasd0twqTZKakfQBkUBjoJR JCOKLcgFmp52jZrxvnHCb1sqIF3SbCCrG0t07nsm3lZE0PLDR6eRWjoMFXL5IqrO peKnW/eZAV2C6ZrJ4C719yeKJerj97oNHkPRMcVw4LH+hRDyEFFoJJ+/giW08dyV 94gyB6g5lSCp5i2bGk3XNtyVfYHGwrKB6VBq+zpIGGQ== 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=fm2; bh=spV61m G0jRUhZzYytTyhEn+ihN3DsNBNuzcLNwI8qDg=; b=KbtJLwsZQ5o8DpBMY5ppnm mYXYeTzqpgaKvcqav0FJ7zubx+1UBh3q2zeZgH/nLPrWbGgim0H0nwSBjesiIOD7 B9oQLF2GjK7VR19CSCiEAtpKQsaZ0jCPjX9JlN4hcPLmp0T1yWHiB8fMwnUXZmwk /Q0mcgc+aQOXzBPz9gddtzXbl2nWHi6S9rqVR3jgcZ3n+RcuklOAT4GNwt3wJNWM sLltd1/HInjcxZAX/RBTw9aJ0zHOw8PraWkgx4DQ7vFcYTMX36lStGMX1k37T5z+ dfxFvDav9DBoIwgZh/DyVzYWTtrKDUd5J1vxfrpGt+kFq3ladSouWC7O5dqoB/Gw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrtdeggdeghecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttdertd dttddvnecuhfhrohhmpefirhgvghcumffjuceoghhrvghgsehkrhhorghhrdgtohhmqeen ucfkphepkeefrdekiedrkeelrddutdejnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhm X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id D0A8A3280064; Thu, 2 Apr 2020 08:19:45 -0400 (EDT) Date: Thu, 2 Apr 2020 14:19:43 +0200 From: Greg KH To: kipade Subject: Re: Was there a way to bind a shared memory object onto a fixed physical memory address? Message-ID: <20200402121943.GB2773800@kroah.com> References: <59cbc6e1.997d.1713a419e1c.Coremail.kipade@163.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <59cbc6e1.997d.1713a419e1c.Coremail.kipade@163.com> 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 Thu, Apr 02, 2020 at 05:38:31PM +0800, kipade wrote: > As the topic, I want to specify a fixed physical memory space to a shared memory object, which can use > shm_XXX api to access the memory. Of course I do not want to use mmap api to map /dev/mem device > memory into user program. Step back and tell us exactly what problem you have, that you have come up to this type of solution being necessary? What do you think you can solve by doing this? thanks, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies