[fstests PATCH v5 0/2] add test for DAX MAP_SYNC support
by Ross Zwisler
This is the fifth revision of my xfstest adding a test for the new
mmap() MAP_SYNC flag. The previous version can be found here:
https://lists.01.org/pipermail/linux-nvdimm/2017-November/013329.html
Changes since v4:
- Test for dm-log-writes + DAX support in the spirit of
_require_scratch_dax() instead of relying on specific module version
number. (Eryu)
- Print out the missing mark name in the error output of
_log_writes_replay_log(). (Eryu)
- Go back to using the output from "du -sh" to test our file block
allocations. The "stat -c %s" I was using in v4 was broken if the
file existed and only had partial block allocations, and the number
of blocks reported by "stat -c %b" can vary based on the block size.
- Move the test number to 999 to avoid rebasing collisions. Feel free
to renumber as necessary when merging.
I've updated the links at the bottom of this mail to point to the most
recent version of my xfsprogs changes and to the current version of this
series.
---
The purpose of this series is to exercise the new MAP_SYNC mmap()
functionality [1]. It adds a test which uses dm-log-writes to try and
replay filesystem metadata operations for a file that is being written via
mmap().
If MAP_SYNC is active the dm-log-writes replay will recreate the file's
block allocations and you'll end up with a test file which is a known
size.
If MAP_SYNC is not active the metadata writes will most likely be lost and
the replay will either fail to create the test file at all or it will may
be smaller. In all of my testing the file simply doesn't exist on the
replay if MAP_SYNC is ommited.
This test relies on a kernel with both the MAP_SYNC mmap() functionality
and the DAX enabling in dm-log-writes. These both appear in kernel
v4.15-rc*. For ease of testing I've posted a kernel that is v4.14 plus
just those two patch series [2].
This test also relies on xfsprogs having support for MAP_SYNC and for
dm-log-writes. I've posed a tree adding that support [3]. This xfsprogs
series is still under review so if the xfs_io interfaces change this
test will of course need to be updated as well.
Lastly, I've also posted a working version of this series [4].
[1]: https://lists.01.org/pipermail/linux-nvdimm/2017-November/013164.html
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/linux.git/log/?h=...
[3]: https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/xfsprogs-dev.git/...
[4]: https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/xfstests-dev.git/...
Ross Zwisler (2):
dm-log-writes: only replay log to marks that exist
generic: add test for DAX MAP_SYNC support
common/dmlogwrites | 24 +++++++++++++++
tests/generic/999 | 82 +++++++++++++++++++++++++++++++++++++++++++++++++++
tests/generic/999.out | 3 ++
tests/generic/group | 1 +
4 files changed, 110 insertions(+)
create mode 100755 tests/generic/999
create mode 100644 tests/generic/999.out
--
2.14.3
2 years, 10 months
[RFC PATCH v2 0/7] ndctl: nvdimmd: notify/monitor the feathers of over threshold event
by QI Fuli
Hi, here is my second version of nvdimm daemon, It would be appreciated
if you could check it.
Change log since v1:
- Adding a config file(/etc/nvdimmd/nvdimmd.conf)
- Using struct log_ctx instead of syslog()
- Using log_syslog() to save the notify messages to syslog
- Using log_file() to save the notify messages to special file
- Adding LOG_NOTICE level into log_priority
- Using automake instead of Makefile
- Adding a new util file(nvdimmd/util.c) including helper functions needed
for nvdimm daemon.
- Adding nvdimmd_test program
---
This is a patch set of nvdimmd, a tiny daemon to monitor the features of over
threshold events. When an over thershold event fires, nvdimmd will output the
notification including dimm health status to syslog or a special file to
users' configuration. Users can choose the output format to be structured json
or text.
Here are out put samples.
- json format:
2017/11/10 11:15:03 [28065] log_notify: nvdimm dimm over threshold notify
{
"dev":"nmem1",
"id":"cdab-0a-07e0-feffffff",
"handle":1,
"phys_id":1,
"health":{
"health_state":"non-critical",
"temperature_celsius":23,
"spares_percentage":75,
"alarm_temperature":true,
"alarm_spares":true,
"temperature_threshold":40,
"spares_threshold":5,
"life_used_percentage":5,
"shutdown_state":"clean"
}
}
- text format:
2017/11/10 16:21:53 [12479] log_notify: nvdimm dimm over threshold notify
dev: nmem1
health_state: non-critical
spares_percentage: 75
TODO list:
- The dimms to monitor should be filtered by namespace and region
- Add more information into the notify message
- Make nvdimmd_test an ndctl command or an option of ndctl inject-error
QI Fuli (7):
ndctl: nvdimmd: add LOG_NOTICE level into log_priority
ndctl: nvdimmd: add nvdimmd necessary util functions
ndctl: nvdimmd: add nvdimmd necessary functions
ndctl: nvdimmd: add body file of nvdimm daemon
ndctl: nvdimmd: add nvdimmd config file
ndctl: nvdimmd: add the unit file of systemd for nvdimmd service
ndctl: nvdimmd: add a temporary test for nvdimm daemon
Makefile.am | 2 +-
configure.ac | 1 +
nvdimmd/Makefile.am | 47 ++++++++
nvdimmd/libnvdimmd.c | 315 ++++++++++++++++++++++++++++++++++++++++++++++++
nvdimmd/libnvdimmd.h | 53 ++++++++
nvdimmd/nvdimmd.c | 112 +++++++++++++++++
nvdimmd/nvdimmd.conf | 25 ++++
nvdimmd/nvdimmd.service | 7 ++
nvdimmd/nvdimmd_test.c | 142 ++++++++++++++++++++++
nvdimmd/util.c | 80 ++++++++++++
nvdimmd/util.h | 33 +++++
util/log.c | 2 +
util/log.h | 3 +
13 files changed, 821 insertions(+), 1 deletion(-)
create mode 100644 nvdimmd/Makefile.am
create mode 100644 nvdimmd/libnvdimmd.c
create mode 100644 nvdimmd/libnvdimmd.h
create mode 100644 nvdimmd/nvdimmd.c
create mode 100644 nvdimmd/nvdimmd.conf
create mode 100644 nvdimmd/nvdimmd.service
create mode 100644 nvdimmd/nvdimmd_test.c
create mode 100644 nvdimmd/util.c
create mode 100644 nvdimmd/util.h
--
2.9.5
2 years, 10 months
转发：建立个人的领导风格与魅力
by 计元毅
---- 原邮件信息 -----
发件人:计元毅<qdekunt(a)symv.com>
收件人:"linux-nvdimm" <linux-nvdimm(a)lists.01.org>;
发送时间:4:00:36
现代管理者沟通影响力与领导力提升
报 名 详 细 信 息 请 阅 读 附 件
课程目标：
² 解团队的本质与运作精神
² 提升管理者的沟通能力
² 学习如何扮演好团队领导的角色，了解领导的内涵，明白管理与领导的差异
² 协助建立个人的领导风格与魅力，掌握情景领导的运用技巧
² 了解自我及他人的性格，提升领导艺术
² 了解管理团队冲突，通过有效的管理来提升团队绩效
课程大纲：
1. 揭开团队的面纱
1) 团队的概念和构成要素
2) 团队与群体的区别
3) 团队的类型
2. 团队的发展阶段
1) 团队的成立期
2) 团队的动荡期
3) 团队的稳定期
4) 团队的高产期
5) 团队的调整期
3. 团队领导的方式认知
1) 领导与管理的差别
2) 领导者的权力与权威
3) 团队领导者的角色与职责
4. 情景领导
1) 何谓情景领导
2) 情景领导的两个纬度
² 指令
² 支持
3) 情景领导的四种风格
² 指令
² 教练
² 支持
² 授权
4) 分析解剖自我的领导风格与型态
² 领导风格与型态测试
² 各类领导风格与型态说明
5) 针对不同类型部属与情景实施不同的领导风格
² 绩效矩阵分析
² 针对不同类型部属展现不同的情景风格
5. 人际相处的情景领导艺术
1) 性格与人际相处的关系
2) 了解自己的性格
² 性格测试
² 解读性格
3) 如何调整性格的缺陷，展现魅力
4) 如何与不同性格类型的人相处
6. 有效的沟通
1) 何谓有效的沟通
2) 沟通中的倾听与说的技巧
² 同理心的倾听要点
² 合作性的说服技巧
3) 如何管理组织冲突
² 认知冲突
² 冲突演变与处理技巧
² 冲突的处理的五大适用策略分析
4) 性格与沟通
² 了解自己的性格
² 解读性格
² 如何与不同性格类型的人相处
² 如何调整与克服性格的缺陷
7. 团队冲突管理
1) 正确认识冲突
² 何谓冲突？
² 传统观念与现代观念对冲突认识比较
2) 面临冲突的常见反应模式
² 竞争
² 回避
² 顺从
² 妥协
² 合作
3) 了解自我的冲突反应模式（测试）
² 通过测试了解自我在面临冲突是的反应模式
4) 面对冲突时的错误心态与行为（征服/回避/交易/遮盖/演戏）
5) 冲突的常见类型
² 建设性冲突
² 破坏性冲突
² 情绪性冲突
² 实质性冲突
6) 冲突解决的三种策略
² 侵略
² 退缩
² 积极
7) 如何通过引发建设性冲突来提升团队绩效
² 冲突与绩效的关系
² 何时引发建设性冲突
² 如何引发建设性冲突
8) 解决冲突时的正确方法与步骤
² 对事不对人
² 从对方的立场出发考虑问题
² 权衡双方的利益，找出共同的目标
² 商谈时双方注意维持充分自由的环境
² 重新考虑优先顺序
² 做出协议
² 追踪协议
讲师介绍：邹老师
高级企业管理培训师
• 曾担任直销公司总部讲师
• 长期担任欧美企业全国培训部负责人
• EWS课程国内培训第一人
• 强思企管 高级讲师
讲师概述：
超过9年企业培训经历，长期服务于欧美零售企业和大型制造业。他成功地把销售和管理中的情绪管理、性格色彩、沟通技巧等融合在培训课程的点点滴滴，使得课程更加生动并引起学员的共鸣。学员在收获课程知识的同时往往掌握到更多高附加值的技能。累计学员超过10万人次，年平均培训场次超过150场，是客户公认的”最受欢迎的讲师之一”。
学员心声：
“老师讲得非常好，生动，具体，课程内容贴近工作。”
----美乐家（中国）HR 经理 Angelina
“邹老师为我们不同地区的员工定制的课程很有针对性，我参加了武汉分公司的培训，很震撼。”
----光明乳业 人力资源经理 侯海敏
“一直觉得跨部门沟通很重要，自己一直也很重视这一点，人际关系还算不错。但没想到听了老师的课才意识到原来部门沟通还有这么多门道。自己之前的很多做法还是有待提高的。受益匪浅！”
---- 摘自光明乳业（北京区）学员反馈
“The training is both wonderful and amazing！”
---- Wal-Mart China CEO Sean Clark 沃尔玛中国区总裁柯俊贤
“邹老师的授课深入浅出，给我司管理者留下了深刻的印象！”
---- 航星工业 人力资源刘经理
授课形式：
讲解及实例分析、讲解及案例分析、分组练习、实例和练习、讲解及实例、讲解及应用。
2 years, 10 months
[PATCH] acpi, nfit: fix health event notification
by Dan Williams
Integration testing with a BIOS that generates injected health event
notifications fails to communicate those events to userspace. The nfit
driver neglects to link the ACPI DIMM device with the necessary driver
data so acpi_nvdimm_notify() fails this lookup:
nfit_mem = dev_get_drvdata(dev);
if (nfit_mem && nfit_mem->flags_attr)
sysfs_notify_dirent(nfit_mem->flags_attr);
Add the necessary linkage when installing the notification handler and
clean it up when the nfit driver instance is torn down.
Cc: <stable(a)vger.kernel.org>
Cc: Toshi Kani <toshi.kani(a)hpe.com>
Cc: Vishal Verma <vishal.l.verma(a)intel.com>
Fixes: ba9c8dd3c222 ("acpi, nfit: add dimm device notification support")
Reported-by: Daniel Osawa <daniel.k.osawa(a)intel.com>
Signed-off-by: Dan Williams <dan.j.williams(a)intel.com>
---
drivers/acpi/nfit/core.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c
index ff2580e7611d..947ea8a92761 100644
--- a/drivers/acpi/nfit/core.c
+++ b/drivers/acpi/nfit/core.c
@@ -1670,6 +1670,11 @@ static int acpi_nfit_add_dimm(struct acpi_nfit_desc *acpi_desc,
dev_name(&adev_dimm->dev));
return -ENXIO;
}
+ /*
+ * Record nfit_mem for the notification path to track back to
+ * the nfit sysfs attributes for this dimm device object.
+ */
+ dev_set_drvdata(&adev_dimm->dev, nfit_mem);
/*
* Until standardization materializes we need to consider 4
@@ -1755,6 +1760,7 @@ static void shutdown_dimm_notify(void *data)
if (adev_dimm)
acpi_remove_notify_handler(adev_dimm->handle,
ACPI_DEVICE_NOTIFY, acpi_nvdimm_notify);
+ dev_set_drvdata(&adev_dimm->dev, NULL);
}
mutex_unlock(&acpi_desc->init_mutex);
}
2 years, 10 months
revamp vmem_altmap / dev_pagemap handling
by Christoph Hellwig
Hi all,
this series started with two patches from Logan that now are in the
middle of the series to kill the memremap-internal pgmap structure
and to redo the dev_memreamp_pages interface to be better suitable
for future PCI P2P uses. I reviewed them and noticed that there
isn't really any good reason to keep struct vmem_altmap either,
and that a lot of these alternative device page map access should
be better abstracted out instead of being sprinkled all over the
mm code.
Please review carefully, this has only been tested with my legacy
e820 NVDIMM system.
2 years, 10 months
[PATCH] libnvdimm, dax: fix 1GB-aligned namespaces vs physical misalignment
by Dan Williams
The following namespace configuration attempt:
# ndctl create-namespace -e namespace0.0 -m devdax -a 1G -f
libndctl: ndctl_dax_enable: dax0.1: failed to enable
Error: namespace0.0: failed to enable
failed to reconfigure namespace: No such device or address
...fails when the backing memory range is not physically aligned to 1G:
# cat /proc/iomem | grep Persistent
210000000-30fffffff : Persistent Memory (legacy)
In the above example the 4G persistent memory range starts and ends on a
256MB boundary.
We handle this case correctly when needing to handle cases that violate
section alignment (128MB) collisions against "System RAM", and we simply
need to extend that padding/truncation for the 1GB alignment use case.
Cc: <stable(a)vger.kernel.org>
Fixes: 315c562536c4 ("libnvdimm, pfn: add 'align' attribute...")
Reported-and-tested-by: Jane Chu <jane.chu(a)oracle.com>
Signed-off-by: Dan Williams <dan.j.williams(a)intel.com>
---
drivers/nvdimm/pfn_devs.c | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/drivers/nvdimm/pfn_devs.c b/drivers/nvdimm/pfn_devs.c
index 65cc171c721d..5ba9ab7af736 100644
--- a/drivers/nvdimm/pfn_devs.c
+++ b/drivers/nvdimm/pfn_devs.c
@@ -582,6 +582,12 @@ static struct vmem_altmap *__nvdimm_setup_pfn(struct nd_pfn *nd_pfn,
return altmap;
}
+static u64 phys_pmem_align_down(struct nd_pfn *nd_pfn, u64 phys)
+{
+ return min_t(u64, PHYS_SECTION_ALIGN_DOWN(phys),
+ ALIGN_DOWN(phys, nd_pfn->align));
+}
+
static int nd_pfn_init(struct nd_pfn *nd_pfn)
{
u32 dax_label_reserve = is_nd_dax(&nd_pfn->dev) ? SZ_128K : 0;
@@ -637,13 +643,16 @@ static int nd_pfn_init(struct nd_pfn *nd_pfn)
start = nsio->res.start;
size = PHYS_SECTION_ALIGN_UP(start + size) - start;
if (region_intersects(start, size, IORESOURCE_SYSTEM_RAM,
- IORES_DESC_NONE) == REGION_MIXED) {
+ IORES_DESC_NONE) == REGION_MIXED
+ || !IS_ALIGNED(start + resource_size(&nsio->res),
+ nd_pfn->align)) {
size = resource_size(&nsio->res);
- end_trunc = start + size - PHYS_SECTION_ALIGN_DOWN(start + size);
+ end_trunc = start + size - phys_pmem_align_down(nd_pfn,
+ start + size);
}
if (start_pad + end_trunc)
- dev_info(&nd_pfn->dev, "%s section collision, truncate %d bytes\n",
+ dev_info(&nd_pfn->dev, "%s alignment collision, truncate %d bytes\n",
dev_name(&ndns->dev), start_pad + end_trunc);
/*
2 years, 10 months
RFC: dev_pagemap reference counting
by Christoph Hellwig
Hi Dan,
maybe I'm missing something, but it seems like we release the reference
to the previously found pgmap before passing it to get_dev_pagemap again.
Can you check if my findings make sense?
2 years, 10 months
[RFC PATCH 0/4] Teach EDAC driver about NVDIMMs
by Tony Luck
A Skylake server may have some DIMM slots filled with NVDIMMs
instead of normal DDR4 DIMMs. These are enumerated differently
by the memory controller.
Sadly there isn't an easy way to just peek at some memory controller
register to find the size of these DIMMs, so we have to rely on the
NFIT and SMBIOS tables to get that information.
This series only tackles the topology function of the EDAC
driver. A later series of patches will fix the address translation
parts so that errors in NVDIMMs will be reported correctly.
It's marked "RFC" because it depends on the new ACPCIA version 20171110
which has only just made it to Rafael's tree.
Some of you may only care about some of the parts that touch code you
maintain, but I copied you on all four because you might like to see
the bigger picture.
Tony Luck (4):
acpi, nfit: Add function to look up nvdimm device and provide SMBIOS
handle
firmware: dmi: Add function to look up a handle and return DIMM size
edac: Add new memory type for non-volatile DIMMs
EDAC, skx_edac: Detect non-volatile DIMMs
drivers/acpi/nfit/core.c | 27 +++++++++++++++++++++
drivers/edac/Kconfig | 2 ++
drivers/edac/edac_mc.c | 1 +
drivers/edac/edac_mc_sysfs.c | 3 ++-
drivers/edac/skx_edac.c | 56 ++++++++++++++++++++++++++++++++++++++++----
drivers/firmware/dmi_scan.c | 29 +++++++++++++++++++++++
include/acpi/nfit.h | 19 +++++++++++++++
include/linux/dmi.h | 2 ++
include/linux/edac.h | 3 +++
9 files changed, 136 insertions(+), 6 deletions(-)
create mode 100644 include/acpi/nfit.h
base-commit: 3fc70f8be59950ee2deecefdddb68be19b8cddd1
--
2.14.1
2 years, 10 months
答复:/ linux-nvdimm
by 高朦羽
有效调岗调薪、裁员解雇及违纪问题员工处理技巧
2017年12月15--16日-----广州
2017年12月18--19日-----上海
2017年12月22--23日-----深圳
2017年12月29--30日-----北京
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
【学员对象】董事长、总经理、副总经理、人力资源总监/经理/专员及人事行政管理人员、工会干部、法务人员及相关管理人员、相关律师等。
【费====用】3200元/1人
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
●培-训-报-名-中-心:
报名咨询电话：0755-61288035 010-51661863 021-31261580
手机：18890700600 （微信同号）赵先生
在线咨询 QQ：6983436 报名信箱：6983436(a)qq.com (报名请回复报名表）
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
【授_课_专_家_介_绍】资_深_劳_动_法_实_战_专_家 钟永棣
国内著名劳动法、劳动关系与劳动争议实战专家；劳动仲裁员、企业劳动争议预防应对专家、高级人力资源管理师、高级劳动关系协调师；国内第一批倡导、传播、实施“国家劳动法与企业薪酬绩效管理有机整合”的先行者；国内原创型、实战型、顾问型的培训师。
现任劳律通法律顾问服务中心首席顾问、上海德禾翰通律师事务所董事顾问；兼任时代光华、深圳外商投资企业协会、广州市劳动保障学会、广州市人力资源市场服务中心、广州市就业训练中心、广东省人力资源管理协会、香港工业总会、中山大学、浙江大学、华南理工大学等200多家培训公司、行业协会、有关机构单位的长期签约讲师\特聘顾问。
钟老师精通劳动政策法律法规和劳动仲裁、诉讼程序，擅长劳动用工风险的有效预防与劳动争议案件的精准应对，善于把劳动法律法规与企业人力资源管理有机整合，通晓企业劳动争议防范机制的构建和劳动用工管理体系的修正完善。钟老师经常在客户办公现场、培训现场为客户、学员即时起草、审查、修改相关制度、合同、文书，或分析具体案件，提出精准应对思路；钟老师独到的现场的专业功底，每次都赢得广大客户、学员发自内心的好评与100%的信服！
科班出身的钟老师，2000年至今一直从事与劳动法、劳动关系与劳动争议有关的工作；曾任劳动行政部门专职劳动仲裁员，曾获“广州市优秀劳动仲裁员”称号，期间审裁劳动争议案件400多宗；多年来累计代理劳动争议500多宗，参与薪酬绩效咨询项目20多个，审查完善400多家企业的人力资源管理规章制度。个人长期担任30多家（累计200多家）企业单位的人力资源管理法律顾问；以钟老师领衔的专家队伍，长期为企事业单位提供劳动法常年顾问及各种劳资专项咨询服务，客户满意度高达95%。
2008年至今，钟老师每年授课约100-130天。钟老师将枯燥的劳动政策法规溶入实际管理案例当中，将人力资源管理与劳动法有机地整合在一起；课程内容80%为真实案例、20%为必备的重点法条；学员参与讨论、互动，课程生动有趣，深入浅出，实战型超强，让学员即时学以致用！课程满意度高达95%，众多学员均表示：“第一次听到如此实战、实用、实效的劳动法课程！钟老师非常务实、不说教、没有商业味道，终于听到了让我不再后悔的精彩课程！”
钟老师先后在《广州日报》《南方都市报》《中国社会科学报》《人力资源》《香港工业总会月刊》等报刊、杂志、媒体发表专业文章或采访稿100多篇。
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
● 课 程 大 纲：
（共2天，20个以上经典案例）
专题一：违纪违规问题员工处理
1.劳动者往往拒绝签收处分、解雇通知书，如何应对？
2.问题员工往往拒绝提交《检讨书》或否认违纪违规事实，企业该如何收集证据？
3.对于违纪员工，应该在什么时间内处理？
4.怎样理解“严重违反用人单位的规章制度”?
5.如何在《惩罚条例》中描述“一般违纪”、“较重违纪”及“严重违纪”？
6.怎样理解与操作“严重失职，营私舞弊，给用人单位造成重大损害”？
7.如何界定“重大损害”，“重大损害”是否必须体现为造成直接的经济损失？
8.如何追究“严重失职、严重违纪违规”者的法律责任？
9.能否直接规定“禁止兼职，否则视为严重违纪违规”？
10.直线部门经理擅自口头辞退员工，仲裁机构往往认定企业非法解雇，企业该如何做，才避免案件败诉？
11.劳动者不辞而别、无故旷工，却主张被企业口头解雇，往往得到仲裁机构的支持，企业该如何做，才避免案件败诉？
12.劳动者被行政拘留、刑事拘留、司法拘留期间，劳动关系如何处理？
13.“录音录象”证据，仲裁与法院是否采信；企业内部OA系统上的资料能否作为证据使用；电子邮件、手机短信能否作为证据使用？
专题二：绩效管理与岗位调整
1.企业单方调整岗位，员工往往可被迫解除合同并索赔经济补偿，如何规避？
2.调岗时没有书面确认，员工到新岗位工作2个月后能否要求恢复到原岗位？
3.可否对“三期内”女职工进行调岗、调薪？
4.与员工协商调岗前，需要做哪些准备工作？
5.员工认同绩效结果，为什么在“不胜任工作”引发的争议中还是败诉？
6.为什么企业根据绩效结果支付员工绩效奖金，最终被认定非法克扣工资？
7.法律上如何证明劳动者“不能胜任工作”？
8.对绩效考核不合格的员工，如何合法辞退？
9.绩效正态分布往往强制划分5%的员工为不合格者，是否合法？
10.不称职等同于不胜任工作吗？
专题三：工资福利与薪酬调整
1.工资总额包括哪些工资明细？
2.新进员工薪资管理问题及处理技巧；
3．调整工作岗位后，如何单方调薪、降薪？
4．如何通过薪酬调整处理员工失职、违纪等问题？
5．什么情况下可以扣减员工的工资？
6．值班算不算加班，如何防范风险？
7．未经单位确认，劳动者自行加班，能否主张加班费？
8．年薪制的员工能否主张加班费？
9．如何设计工资构成以降低加班费成本？
10．员工主张入职以来的加班费，如何应对？
11．员工在工作日下班后加班，能否安排补休而不支付加班费？
12.内部规定“已离职员工无权获取年终奖”，真的有效吗？
专题四：工作时间与休息休假
1.每周6天，每天7小时，究竟加班了2小时还是7小时？
2.工作日停电停工休息，能否要求员工周日上班，补回停工休息日？
3.综合工时下，法定节假日是否属于总的工作时间内？
4.病假、医疗期、工伤假的享受条件及风险管控；
5.如何预防与应对员工泡病假？
6.产假、年休假、婚丧假的享受条件及风险管控；
7.实习生、反聘人员能否享受年休假？
8.用人单位是否必须批准员工请事假？
9.请事假，当月工资是以实际出勤天数计算还是以工资总额减去缺勤天数计算？
专题五：经济补偿
1.用人单位需向劳动者支付经济补偿的情形有哪些？
2.什么情况下用人单位需支付两倍的经济补偿？
3.违法解除下是否存在代通知金？
4.劳动者可否同时向用人单位主张经济补偿和赔偿金？
5.经济补偿计算的基数及标准如何确定？
6. 解除前12个月内员工休过医疗期，其平均工资如何认定？
7.经济补偿年限最高不超过十二年的适用范围？
8.如何计算《劳动合同法》生效前后的经济补偿年限？
9.如何理解“六个月以上不满一年的，按一年计算；不满六个月的，支付半个月工资的经济补偿”？
10.劳动合同法环境下“50%额外经济补偿金”是否继续适用？
专题六：规章制度与员工手册
1.企业人力资源、劳动用工管理制度常见的误区有哪些？
2.人力资源、劳动用工管理制度应该包括哪些必备内容？
3.制定规章制度的程序要求给用人单位带来哪些风险，如何应对？
4.非国有用人单位如何组建“职工代表大会”？
5.二级单位的员工是否有义务遵守集团公司的规章制度？
6.如何公示或告知，更符合仲裁或诉讼的举证要求？
7.规章制度能否规定对员工进行经济处罚？
8.规章制度违反法律法规，劳动者可以被迫解除并索取经济补偿，如何防范？
9.规章制度与员工手册到底有什么区别？
10．规章制度与员工手册应该多长时间修改一次？
专题七：工伤保险条例
1.属于工伤范围的情形有哪些？
2.不得认定为工伤的情形有哪些？
3.员工工作应酬喝酒身亡，是否属于工伤？
4.无照驾驶与驾驶无照车辆受伤，能否认定为工伤?
5.对劳动能力鉴定结果不服，能否提起行政诉讼？
6.怎样理解“上下班途中”，怎样控制期间的风险？
7.发生工伤事故，用人单位需承担哪些费用？
8.对于第三方造成的工伤事故，劳动者能否要求用人单位支付工伤待遇又同时要求第三方支付人身伤害赔偿？
9.用人单位能否以商业保险理赔款替代职工工伤赔偿待遇？
10.发生工伤事故，双方私下和解，补偿协议该如何签订才有效？
专题八：劳务派遣与业务外包
1.新法下劳务派遣面临的主要风险有哪些？
2.劳务派遣合作协议必须注意的风险细节有哪些？
3.派遣工“第三签”时，能否要求签订无固定期限劳动合同？
4.哪些岗位可以使用派遣工，辅助性、临时性、替代性如何理解与操作？
5.新规定对于同工同酬提出哪些新要求，如何规避同工同酬风险？
6.采用劳务派遣用工方式，能否异地参保？
7.用工单位如何行使对派遣员工的退还或退换权？
8.部分劳务公司很可能面临关闭停业，原来的派遣工的劳动关系如何处理？
9.业务外包与劳务派遣的本质区别有哪些？
10.如何筛选业务外包供应商，需考察哪些细节要点？
11.用工单位如何应对派遣合作争议和劳动争议？
12.如何避免与劳务派遣工或承包方员工形成双重劳动关系？
--- 报 名 回 执 表 ----
如需发E-mail可发至6983436(a)qq.com
(請务必填写貴公司全称和参会學员真实姓名,谢谢！)
我单位共_______人报名参加________年____月 _____日 在 ______
举办的“有效调岗调薪、裁员解雇及违纪问题员工处理技巧”高级研修班
单位名称（即发票抬头）：_____________________________________________（请务必正楷字填写正确）
联 系 人：______________ 联系电话：________________ 手 机：_________________
E-mail: ___________________________________________ 传 真：_________________
参会代表：______________ 移动电话：________________ 职 务: _________________
参会代表：______________ 移动电话：________________ 职 务: _________________
参会代表：______________ 移动电话：________________ 职 务: _________________
参会代表：______________ 移动电话：________________ 职 务: _________________
参会代表：______________ 移动电话：________________ 职 务: _________________
共计费用：___________ 元整。 付款方式：□ 现 金 □ 转 帐（请选择打“√”）
备注:
1.请您把报名回执认真填好后回传我司，为确保您报名无误,请您再次电话确认!
2 years, 10 months
[fstests PATCH v4 0/4] add test for DAX MAP_SYNC support
by Ross Zwisler
The purpose of this series is to exercise the new MAP_SYNC mmap()
functionality [1]. It adds a test which uses dm-log-writes to try and
replay filesystem metadata operations for a file that is being written via
mmap().
If MAP_SYNC is active the dm-log-writes replay will recreate the file's
block allocations and you'll end up with a test file which is a known
size.
If MAP_SYNC is not active the metadata writes will most likely be lost and
the replay will either fail to create the test file at all or it will may
be smaller. In all of my testing the file simply doesn't exist on the
replay if MAP_SYNC is ommited.
This test relies on a kernel with both the MAP_SYNC mmap() functionality
and the DAX enabling in dm-log-writes. These will both appear in kernel
v4.15-rc1. For ease of testing I've posted a kernel that is v4.14 plus
just those two patch series [2].
This test also relies on xfsprogs having support for MAP_SYNC and for
dm-log-writes. I've posed a tree adding that support [3]. This xfsprogs
series is still under review so if the xfs_io interfaces change this
test will of course need to be updated as well.
Lastly, I've also posted a working version of this series [4].
Changes since v3:
- Enhanced xfs_io with MAP_SYNC and dm-log-writes functionality instead of
creating a one-off test program. (Dave Chinner)
- Improved dm target version checking. (Amir)
- Fixed dm-log-writes replay issue, some general cleanup, broke changes
out into a series.
[1]: https://lists.01.org/pipermail/linux-nvdimm/2017-November/013164.html
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/linux.git/log/?h=...
[3]: https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/xfsprogs-dev.git/...
[4]: https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/xfstests-dev.git/...
Ross Zwisler (4):
common/rc: add _scratch_has_mount_option()
dm-log-writes: only replay log to marks that exist
dm-log-writes: allow DAX to be used when possible
generic: add test for DAX MAP_SYNC support
common/dmlogwrites | 9 +++--
common/rc | 33 ++++++++++++++++--
doc/requirement-checking.txt | 5 +--
tests/generic/468 | 83 ++++++++++++++++++++++++++++++++++++++++++++
tests/generic/468.out | 3 ++
tests/generic/group | 1 +
6 files changed, 128 insertions(+), 6 deletions(-)
create mode 100755 tests/generic/468
create mode 100644 tests/generic/468.out
--
2.9.5
2 years, 10 months
