From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=linux.ibm.com (client-ip=148.163.156.1; helo=mx0a-001b2d01.pphosted.com; envelope-from=mspinler@linux.ibm.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.ibm.com Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4590P46BMlzDqY1 for ; Fri, 24 May 2019 05:46:15 +1000 (AEST) Received: from pps.filterd (m0098396.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x4NJhkPm016976 for ; Thu, 23 May 2019 15:46:13 -0400 Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by mx0a-001b2d01.pphosted.com with ESMTP id 2sp0gwuf4q-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 23 May 2019 15:46:12 -0400 Received: from localhost by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 23 May 2019 20:46:12 +0100 Received: from b03cxnp08026.gho.boulder.ibm.com (9.17.130.18) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Thu, 23 May 2019 20:46:10 +0100 Received: from b03ledav002.gho.boulder.ibm.com (b03ledav002.gho.boulder.ibm.com [9.17.130.233]) by b03cxnp08026.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x4NJk9k922217172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 23 May 2019 19:46:09 GMT Received: from b03ledav002.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B0A15136051 for ; Thu, 23 May 2019 19:46:09 +0000 (GMT) Received: from b03ledav002.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 974CF13604F for ; Thu, 23 May 2019 19:46:09 +0000 (GMT) Received: from [9.10.99.36] (unknown [9.10.99.36]) by b03ledav002.gho.boulder.ibm.com (Postfix) with ESMTP for ; Thu, 23 May 2019 19:46:09 +0000 (GMT) From: Matt Spinler Subject: phosphor-logging extensions To: OpenBMC Maillist Date: Thu, 23 May 2019 14:46:09 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-TM-AS-GCONF: 00 x-cbid: 19052319-8235-0000-0000-00000E9D579B X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00011150; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000286; SDB=6.01207582; UDB=6.00634203; IPR=6.00988562; MB=3.00027022; MTD=3.00000008; XFM=3.00000015; UTC=2019-05-23 19:46:11 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19052319-8236-0000-0000-000045B13FEB Message-Id: <4b80be47-ef72-afc1-54ca-a658efb98015@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-23_16:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=762 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905230127 X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2019 19:46:17 -0000 Hi, In the past I have written about phosphor-logging library plugins. We've now morphed that into having logging extensions that live in the phosphor-logging repo.  They would be completely compiled out and disabled unless they were explicitly enabled.  The point of these is to allow other log formats to be created without incurring extra D-Bus call overhead. Our use case is for a special Platform Event Log (PEL) format that we have to support on the BMC.  We discussed (a lot) about having a standalone PEL daemon, but the D-Bus overhead was deamed to be too large. I have a prototype of this up at https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-logging/+/2189. I also discuss it in a design document that covers how to handle PEL support at https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/21368.